Hi Stefan, > Concept is: > webserver pubsub client > HTTP Post => PUSH PULL => PUB SUB
What I get from your explanation is, "HTTP client sends streams of work requests that are broken into 1K chunks which whargarble pub-sub whargarble and then whargarble because 0MQ multipart threads whargarble how do I whargarble sockets?" Not trying to be sarcastic, just explaining why no-one has been able to help you here. Please explain what you are actually trying to achieve, not in terms of 0MQ but in terms of the actual overall problem, and we'll be able to help more. Cheers Pieter On Tue, Nov 27, 2012 at 8:26 AM, Stefan de Konink <[email protected]> wrote: > On 11/26/12 22:41, Apostolis Xekoukoulotakis wrote: >> Just buffer the message parts yourself and send them when the last part >> has come. >> Why not do that? > > That requires huge amounts of memory allocation in the webserver, which > also caches the requests. So I am not looking for a different way to > change my program, in either way I must implement a connection pool, > because I also can't afford the socket close. > > Stefan > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
