On 22/07/2009, at 1:11 PM, Chuck Hill wrote:
This works fine, _except_ that the state needs to persist across
scheduled re-starts. I will look at storing the state in the
database instead.
Restarts and multiple instances, no? Otherwise they would need to
login to each instance.
Ah, thanks Chuck---another nail in the coffin of my original
implementation. I'm currently only deploying a single instance, so I
hadn't hit that problem yet. Obviously I do need to use the DB here.
Presumably someone has crossed this bridge before. What do others do
for this kind of thing? An AppState EO of some kind? (How would I
ensure that remained a singleton?) Direct DB access?
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
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]
