• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: XCode 3 WO version?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode 3 WO version?


  • Subject: Re: XCode 3 WO version?
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 9 Aug 2006 10:22:36 -0700


On Aug 9, 2006, at 9:35 AM, Mankit Sze wrote:


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.

Are there any hooks for when threads get assigned? Wonder uses some ThreadLocal storage for editing context management (I think, Anjo will of course know the real details). This may cause it some problems.


Chuck



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:
40global-village.net


This email sent to email@hidden

--
Coming in 2006 - an introduction to web applications using WebObjects and Xcode http://www.global-village.net/wointro


Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects




_______________________________________________ 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
  • Follow-Ups:
    • Re: XCode 3 WO version?
      • From: Anjo Krank <email@hidden>
References: 
 >XCode 3 WO version? (From: Anjo Krank <email@hidden>)
 >Re: XCode 3 WO version? (From: Mankit Sze <email@hidden>)
 >Re: XCode 3 WO version? (From: Anjo Krank <email@hidden>)
 >Re: XCode 3 WO version? (From: Mankit Sze <email@hidden>)

  • Prev by Date: Re: XCode 2.4: EOModeler & EOModeler Plugin deprecated?
  • Next by Date: Re: XCode 3 WO version?
  • Previous by thread: Re: XCode 3 WO version?
  • Next by thread: Re: XCode 3 WO version?
  • Index(es):
    • Date
    • Thread