• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Your session has timed out.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Your session has timed out.


  • Subject: Re: Your session has timed out.
  • From: email@hidden (Anjo Krank)
  • Date: Wed, 4 Jun 2003 22:27:20 +0200
  • Xx-reply-to: email@hidden

FWIW:

David Teran checked in the new ERXObjectStoreCoordinatorPool into Project Wonder yesterday. It should take care well of the nitty-gritty of doing multithreaded EOF...and it's a really small class for what it's doing.

Cheers, Anjo


Am Mittwoch, 04.06.03 um 21:39 Uhr schrieb Jonathan Rochkind:

At 11:41 AM 6/4/2003 -0700, Chuck Hill wrote:

3. Use the WOLongResponsePage to generate the report. While this is a
somewhat elegant and appropriate solution it also implicitly makes your app
dispatch requests concurrently. This makes it very important that your app
is threadsafe and all the EOF objects are getting locked properly. You
will be wanting to test this!

It's very tricky to get WOLongResponsePage to work when the long-running-computation involves EOF. With the newly better documented EOF locking APIs, it should be possible somehow, but I haven't had time to figure it out. You can't just do what seems obvious----because if the long running computation has the right locks out on the EOF stack, then the 'update' page's request to see if the computation was done will end up blocking until the computation IS done. Which usually isn't the behavior you want, although if you don't need to show a 'progress bar', it may be sufficient. But it can be tricky to get it working right. I wouldn't reccomend messing around with WOLongResponse for EOF operations unless you have a reasonable idea of what's going on, and have some time to figure it out.


--Jonathan


4. Move the reporting to another reporting only application and increase
the Connect and Receive timeouts. This will prevent the session
restoration errors while not blocking users of the main application.



Chuck

--

Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.

  • Prev by Date: Re: Your session has timed out.
  • Next by Date: Re: Encryption Code Problem
  • Previous by thread: Re: Your session has timed out.
  • Next by thread: A broken pipe message and cannot open a webObjects page
  • Index(es):
    • Date
    • Thread