Re: Snapshot problems - Solved, sort of
Re: Snapshot problems - Solved, sort of
- Subject: Re: Snapshot problems - Solved, sort of
- From: Mike Schrag <email@hidden>
- Date: Sun, 22 Apr 2007 13:32:32 -0400
This seemed like the way to go to me, too, at first. But then I read (see link below) that you couldn't reliably lock an editing context in a page's awake/sleep like in session, because those might not always get called with a one to one correlation (that is, you might somehow have two awake() invocations or two sleep() invocations in a row). Since attributes on EOs in that ec will be getting set when the form values are pulled, I didn't know how to lock correctly if I couldn't lock/unlock in awake/sleep, so I moved all that business to session, as the post suggested.
If you're using wonder, you can just turn on auto-locking and be done w/ it ... You rarely have to even consider locking except in strange threading scenarios with auto-locking. I've posted about this with instructions within the past few weeks (along with a couple other people), so you should be able to find it in the archives. I can't remember if I posted about autolocking on the wotips list, but I might have. Alternatively, you can use MultiECLockManager as described in Chuck's book.
If the application runs great without snapshot reference counting, it tells me that the problem lies in the way EODatabase is managing its snapshot dictionary.
I would say "it tells you the problems lies in snapshot handling," (which covers basically everything in EOF, since EOF is fundamentally a big cache) and not apply guilt on you or EODatabase at this point, because there's just not enough information yet. Well, I guess I can't complain too much. After all, they aren't charging anything for the product any more.
I would lean towards "they haven't changed anything in the product for several years."
ms |
_______________________________________________
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