Re: SO_SNDLOWAT not avalaible; how can i avoid non-blocking sockets
From: Rick Jones (foo_at_bar.baz.invalid)
Date: Mon, 29 Nov 2004 18:47:33 GMT
Przemys?aw R??ycki <firstname.lastname@example.org> wrote:
> Thanks a lot for your answer. You presented handful useful
> solutions. I have chosen even the other one. Now all connections
> are in blocking mode, but each of connections has a thread dedicated
> to it. I hope this will work as expected.
There was a reason I didn't mention threads :) Threads can be quite
convenient, heck, sometimes even useful :) However, "connection per
thread" isn't exactly the most "scalable" of solutions out there. I
personally do not see it as being all that much better than
"connection per process." Just keep that in mind if you decide to
scale your application out to more than a "few" (for some, rather
fluid definition of "few" ) connections.
-- Process shall set you free from the need for rational thought. these opinions are mine, all mine; HP might not want them anyway... :) feel free to post, OR email to raj in cup.hp.com but NOT BOTH...