2012/8/24 Justin Cook <[email protected]>: > On Thursday, 23 August 2012 at 20:22, Andrea Crotti wrote: > > The whole idea behind ZMQ is doing sockets the way the project would like to > think sockets "should" have been done. Why reinvent the wheel when there are > messaging patterns that are used over and over, and if correctly abstracted, > can be mixed and matched to offer considerable solutions. > > Instead of getting down to threading or any more advanced topics > versus 101, you should take an example of "reinventing the wheel" and > show how easy it is to do this with the ZMQ library and > Python. Remember, you only have 30 minutes. Start off by showing > classic patterns that ZMQ supports, what it would take to write it > yourself, what bugs everyone else who has done so has not considered, > and then the nifty ZMQ solution that takes minutes.
Thanks that's a good idea. I could show the classic ventilator-workers-sink program, and how plugging in workers at run-time is still perfectly fine.. If there is time and it's easy enough adding a simple dynamic web page generation that is also subscribed to the results, to see how easy is to extend the topology and get nice results. > > Again, walk before you run. You have 30 minutes. If you want to use > this in an over all example, sure. But, you would have to take a > complete example and use each portion throughout the entire 30 minutes > and finish by saying, "in 30 minutes you have created a scalable > reporting system that efficiently collects data from 1000s of > hosts. Thank you." > Well no I was not clear, I didn't want to show how to implement such a thing for the talk, just use it to show in real-time what is happening. It would be very useful in general I think as a project, and very good to explain to other people that don't know much about it what is going on.. _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
