[tor-bugs] #32534 [Applications/Tor Browser]: settle on one canonical jtorctl

[Tor Bug Tracker & Wiki]

#32534: settle on one canonical jtorctl
-------------------------------------------------+-------------------------
 Reporter:  eighthave                            |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  Android, tbb-mobile, jtorctl,        |  Actual Points:
  TorBrowserTeam202001                           |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by sisbell):

 ANTLR would be the standard one for Java.  The performance isn't great for
 a lot of small, high-speed events due to the startup time of the parser
 (this may have improved since I was using it a couple of years ago). So
 that's one area of caution.

 !https://www.antlr.org/

 Replying to [comment:15 eighthave]:


 > For future work: there are tools for generating Java parsers based on
 the ABNF (Augmented Backus-Naur Form) grammar that the control-spec uses.
 Since it seems there are crasher bugs based on parsing events, it seems
 work trying one of these generated parsers using the control-spec.  It
 claims to be RFC2234 ABNF, which might not be the same as the newer
 RFC5234.  Here are two parser generators that I found that would be worth
 trying:
 > * https://github.com/ldthomas/apg-java
 > * http://www.parse2.com/abnf.shtml

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32534#comment:17>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online