Re: XCode 3 WO version?
Re: XCode 3 WO version?
- Subject: Re: XCode 3 WO version?
- From: Mankit Sze <email@hidden>
- Date: Wed, 9 Aug 2006 09:35:04 -0700
On Aug 9, 2006, at 6:33 AM, Anjo Krank wrote:
Thanks for the info (not that I understand how many threads can
handle one request?).
With the blocking I/O exactly one worker thread will be committed to
service the request from beginning till the end.
With non-blocking I/O when the client stalls, the work thread will
NOT wait for its client. It will recycle itself to the worker thread
pool, so that it can be reassigned to handle another request. When
the above-mentioned client is ready to send more data later, the
worker thread used to service it may be busy servicing other
requests. As a result, the worker thread pool will assign a different
worker thread to continue servicing the request. The idea is to make
all the worker threads working all the time and never get blocked by
other clients.
Yours,
Mankit
Is there any chance to made WO 1.5 or 1.6 compatible for the next
release? AFAIK, it's only three lines in
EOSQLExpression.formatValueForAttribute(), not using obj.toString()
but obj.toPlainString() in case of BigDecimals?
Cheers, Anjo
Am 09.08.2006 um 14:55 schrieb Mankit Sze:
No, it's not. JavaWebObjects.framework is different. Network I/O
are based on non-blocking I/O. The threading model has been
changed as well. More specifically, WOWorkerThread(s) are NOT
being used at all. A single request can be handled by more than
one worker threads coming from a cached thread pool. Besides,
there are new API added to WOApplication for JMX support.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden