Re: Warning: Request will be REDIRECTED to non-refusing instance
Re: Warning: Request will be REDIRECTED to non-refusing instance
- Subject: Re: Warning: Request will be REDIRECTED to non-refusing instance
- From: Daniel Muller <email@hidden>
- Date: Thu, 25 Sep 2003 18:28:13 +0200
Chuck Hill <email@hidden> wrote :
Hi Chuck,
> >Deploy on OS X Server. I tried the "kill -3 {pid}" to dump the
> threads states
> >but nothing in my log file. I suppose the stdout is not redirected to a
> file
> >or if it's the case I don't know which one! I will investigate more
> about
> >this very useful facility.
> >
> Hmmm, that reminds me of something.... Yep, Wojtek posted this solution a
> while back:
[snip]
Nice, it works perfectly! Thank you very much.
> >> Won't EOF's optimistic locking handle this?
> >
> >Yes but only when the changes are saved. I show another page when the
> >ILLRequest is locked just to warn the user that he/she can't modify
> it,
> >otherwise the first user can edit the ILLRequest until he saves the
> >changes. It's why I have to unlock the ILLRequests when the session
> >terminates because sometimes people go to the previous page or just
> >close the window!
> >
> :-)
I'm aware that's not very nice but it works. This project was my first
real application with WO but previously I use to work with EOF and Cocoa.
It's quite different to develop Cocoa than WO application with concurrent
access.
I'm wondering if there is another way to deal with one writer and
many readers, considering that the first who grabs the access should be
able to save all the changes and the others just be able to view only?
> >Why? I load EOs in a normal EC without EOSharedEditingContext,
> >I never change EOs, they come from another database (using a
> fetchspec)
> >and I've set the read only option for all entities in the EO Model
> >(the model is different for this particular database)
> >
> EOSharedEditingContext gets locked for you. Otherwise, read only or not,
> you really should lock the editing contexts. Maybe nothing bad will
> happen
> in this case, but locking won't hurt.
OK, I will follow this wise advice. BTW, the EC lock/unlock in terminate
fixes the deadlock.
Thanks again for your help, comments and tricks!
Cheers,
Daniel
--
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.