Do you think this is a good approach?
1. We implement a CustomRequestHandler that extends
WODirectActionRequestHandler [All our app alls are DAs]
2. In the CustomRequestHandler#handleRequest() method we
conditionally call requestHandlingLock() for all the existing EOF
requests and do not lock for the new Ajax ones?
In short we're trying to reach a situation where any EOF calls block
behind each other like they do today. But any Ajax calls are not
limited by the fact that EOF is single-threaded - they are only
limited by the # of worker threads in the WOA.
I think you're working too hard ... If you're not using EOF, you won't
lock EOF. You don't need to do a custom anything -- just make direct
actions (or Ajax framework component actions) that perform your Ajax
calls. There should be nothing additional you need to do to avoid
lock contention.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
