• 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: WOLongResponse and EO processing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOLongResponse and EO processing


  • Subject: Re: WOLongResponse and EO processing
  • From: Sam Barnum <email@hidden>
  • Date: Wed, 26 May 2004 08:25:58 -0700

You can create your own EODatabaseDataSource and pass that to the WODisplayGroup. Just don't tell the WODisplayGroup to fetch on load, or you'll end up doing 2 fetches.
Alternately, I think you could manually edit the .woo file containing the display group. There's a field in there which looks like it sets the editing context. Haven't tested this method, though.
If you're using D2W on the other hand, it's still going to use session.defaultEditingContext



On May 26, 2004, at 7:24 AM, Chuck Hill wrote:

Yet another reason that I never use WODisplayGroup. Sorry, I don't know what to suggest, maybe a WODisplayGroup user will know...


Chuck


On May 26, 2004, at 1:00 AM, rbr wrote:

Hi Chuck,
that's true. But is there any means to avoid the problem while working with a WODisplayGroup ? It uses a EODatabaseDataSource which in turn seems to always use the session's EOEditingContext by default.
Thanks in advance
Richard



Are you using an editing context from session in the Long Response page? Stay away from that, especially session.defaultEditingContext or you will block request dispatch.


Chuck




On May 24, 2004, at 12:32 AM, email@hidden wrote:


Hi all,

WOLongResponse seems to work only for calculation or time consuming tasks (like prime calculation as Apple example) but when I'm processing EO objects and saving changes, the page is no more refreshed.

A workaround is to increased the receive timeout (default value is 30 secondes) for each instance application but it means there is no progress indicator, and the user is not really aware of which operation is in progress.

Any suggestions or comments about how to deal with a long processing (about 60 secondes) with EO objects, including saving, and displaying progress messages.

Thanks for your suggestions and comments,
Orlando.
_______________________________________________
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.


References: 
 >Re: WOLongResponse and EO processing (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: WOLongResponse and EO processing
  • Next by Date: Re: toggling NSlog for framework
  • Previous by thread: Re: WOLongResponse and EO processing
  • Next by thread: Re: WOLongResponse and EO processing
  • Index(es):
    • Date
    • Thread