Re: ORBit server question



Michael Lausch wrote:
> el> For your specific case, you could just use oneway operations,
> el> which don't have this "wait for reply" problem.
> 
> That's not what i want. I don't care about clients blocking upon their
> own requests (for now). I do care about clients blocking, because the
> server is busy working on a request from another client (deny of
> service attacks come to my mind). Also operations can really last a
> long time because it's used for DB accesses and a query can run for
> quite a time to produce the results wanted.

Thats a threading model setup to be thread per request instead of
thread per server. Phil Dawes just sent out a good description of
where ORBit stands with respect to this...

			- Chad



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]