Petr,
I'm interested in your approach here as I read your explanation page. I personally use python and javascript, and don't find RCStream to complicated. But I have half-built an application that in python reads the RCStream, pumps it into a redis queue, gets the text of the diff for each change, searches in the diff for registered text-phrases, and then rebroadcasts the stream with information about the changed text. That system is very similar to what you have built from the diagram you made. I wonder if we abstracted it in some way we might be able to share a bit of process.
Make a great day, Max Klein ‽ http://notconfusing.com/
On Thu, Jan 15, 2015 at 8:03 AM, Petr Bena benapetr@gmail.com wrote:
And if you don't like XML either and can think of a different format, let me know, I would like to add support for multiple formats, so that programs that would need to access RC feed would need minimum of extra dependencies.
On Thu, Jan 15, 2015 at 5:00 PM, Petr Bena benapetr@gmail.com wrote:
Hi folks,
Most of you probably heard about new stream of RC changes as alternative to IRC: https://wikitech.wikimedia.org/wiki/RCStream
I simply found it complex beyond the edge of usability for most of solutions that use low level languages or frameworks that don't support modern technologies like JSON or websocket.IO and don't want to be overbloated with 3rd libs, so I launched this alternative provider: https://wikitech.wikimedia.org/wiki/XmlRcs
If you aren't using JavaScript or Python and you found new RC provider (RCStream) too complex, you might find this useful.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l