Re: SharedEditingContext Write Locks?
Re: SharedEditingContext Write Locks?
- Subject: Re: SharedEditingContext Write Locks?
- From: Dov Rosenberg <email@hidden>
- Date: Fri, 18 Nov 2005 08:10:45 -0500
- Thread-topic: SharedEditingContext Write Locks?
>
>> It seems that calling objectsForFetchSpecification() to either
>> fetch data
>> into the shared editing context or to refresh it too often is a bad
>> thing.
>> When multiple threads are trying to do the same operation - the EOF
>> deadlock
>> occurs.
>
> deadlock or writer starvation? i.e., readers keep on functioning, yes?
I would assume that the readers would continue to function, but all of our
code is calling objectsForFetchSpecification() so I think the whole thing is
in an EOF deadlock.
>
>> Can anyone think of a reasonable strategy? Besides dumping EOF and
>> using
>> JDBC.
>
> The above wouldn't take too much effort and would give you control
> over the reader/writer starvation problems without having to change
> much else I would think. Hmm.. I might look into that for myself...
>
> with regards,
> --
>
> Lachlan Deck
>
>
_______________________________________________
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