And that's fine, but I still don't see the "need" for ZeroMQ in that example. It's not adding websocket support to a non-real-time web-app. It's only serving as the transport for messages from the webserver to the websocket server. You could accomplish that just fine with a regular TCP connection, which would require less code on the webserver and websocket server. They describe a pub/sub architecture, which is feasable using any of the websocket libraries, in fact, web2py comes with comet support already, so... again, there's not much of a need for ZeroMQ. That's fine if you want to implement something and submit it in contrib. It seems useful for the 'backend' parts to communicate with each other.
http://greg.thehellings.com/2011/04/web2py-websockets-and-socket-io-part-i-basic-display/ On Saturday, April 13, 2013 4:05:45 AM UTC-7, Arnon Marcus wrote: > > Here is an example for an architecture of using ZeroMQ for adding > WebSocket support to a non-real-time web-app, without much change to the > existing code (server is PHP in this case, but the architectural structure > is what's interesting) > > http://socketo.me/docs/push > > And here is a more in-depth and interesting example using python with > gevent: > > > http://blog.pythonisito.com/2011/07/gevent-zeromq-websockets-and-flot-ftw.html > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
