Re: WO bug fixes

On Aug 2, 2005, at 12:37 PM, John Pollard wrote:

> Thanks Chuck, I expect some of the bugs I reported were fixed but the 
> cases not marked as closed. I am hoping for concurrent processing of 
> requests from different sessions, not within the same session. I did 
> have it working some time ago as I got some strange effects of mixed 
> data before I synchronized certain sections of code. Now the settings 
> seem to be ignored by WO as a second short JC request (different 
> session) always queues up behind the greedy long one. Come on 
> everyone, use this great JC technology and demand concurrency!
>
I'm still not quite following.  Is it getting blocked behind a greedy 
EOF request?  EOF is single threaded so concurrency is not likely to 
happen there.  As soon as one thread locks the 
EOObjectStoreCoordinator, all other thread have to wait for _any_ EOF 
access.


Chuck


> At 19:42 02/08/2005, Chuck Hill wrote:
>
>>> My top bug is that asking for requests to be handled concurrently 
>>> for a Java Client application server side is apparently ignored. I 
>>> am sure this was working a few releases ago. I suppose I shouldn't 
>>> hold my breath.
>> I don't think that a lot of people use JC and there are a lot of JC 
>> related bugs.  Probably not a lot of people report that bug so it 
>> gets a low priority.  If you are asking for concurrent dispatch of 
>> requests from a single client (session) that probably won't ever 
>> happen.  WO serializes requests by session.
>
> _______________________________________________
> WebObjects-talk mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>
-- 
Practical WebObjects - a book for intermediate WebObjects developers 
who want to increase their overall knowledge of WebObjects, or those 
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects