On 2016-05-31 12:04, Dominique Pellé wrote: > Does it also affect the command line --api output? or is it only about > the server output?
I forgot about that... I think the '--api' output can stay the same for longer. The code to generate it is quite simple, so there's not that much need for code cleanup, unlike with the HTTP API. Our code of the HTTP API is quite bad now that two versions of the API are supported at the same time. > I don't know how many API users there are, but discontinuing the xml > API is going disrupting in my opinion. I have statistics about the public HTTP API and we already have almost 50% of the traffic going to the new API. Once the Firefox add-on, the Chrome extension and the Android client have been switched to the new API, more than 90% of all requests should end up at the new API. For the remaining users we'll have an announcement and https://languagetool.org/http-api/migration.php as a guide on how to adapt their clients. 2016-10-01 might indeed be too early, as I don't know when we can switch to the new Firefox add-on. I don't want to port the old one to the new API but instead just wait until we can release the Chrome extension for Firefox. Regards Daniel ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
