Le 24/09/2016 à 22:51, Brad Jorsch (Anomie) a écrit :
On Sat, Sep 24, 2016 at 11:41 AM, Andrew Otto otto@wikimedia.org wrote:
So, since most of the dev work for a socket.io implementation is already done, you can see what the protocol would look like here: https://github.com/wikimedia/kasocki#socketio-client-set-up
Kasocki is just a library, the actual WMF deployment and documentation would be more specific about MediaWiki type events, but the interface would be the same. (Likely there would be client libraries to abstract the actual socket.io interaction.)
See, that's the sort of thing I was complaining about. If I'm not using whatever language happens to have a library already written, there's no spec so I have to reverse-engineer it from an implementation. And in this case that seems like socket.io on top of engine.io on top of who knows what else.
socket.io has libraries in several languages. The RCStream shows example for JavaScript and Python: https://wikitech.wikimedia.org/wiki/RCStream#Client
It is true though that a lib has to be written on top of that to be aware of MediaWiki events dialect.