On 11/26/12 20:19, Michel Pelletier wrote: > Can you explain a little more why you want to do this? Why not just > have one socket per thread?
Concept is: webserver pubsub client HTTP Post => PUSH PULL => PUB SUB HTTP Posts come in in huge chunks and get processed by about 1k for each iteration. Multiple request at the same time would block eachother within the same thread. This is not solved by allocating a socket per thread, because that cannot guarantee that the incoming post is sequentially written on the same socket. Data from a different source might be available prior to the previous request being finished. Stefan _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
