Fetching data in WOLongResponsePage
Fetching data in WOLongResponsePage
- Subject: Fetching data in WOLongResponsePage
- From: Art Isbell <email@hidden>
- Date: Fri, 29 Aug 2008 17:16:04 -1000
| I have an app that requires a series of large, slow fetches to produce one of its responses. These fetches are causing unacceptable delays in returning this response. I am unable to improve the fetch speed, so I need to provide feedback to the user during this fetch delay.
WOLongResponsePage seems suited for this task. After fetching approximately 15,000 objects of 10 different types in the WOLongResponsePage, I need to transfer these objects back to the main request-response thread in a manner that won't result in these objects being refetched when referenced. Is there a proven approach?
I have created and locked a new editing context in the WOLongResponsePage's performAction(). I fetch about 15,000 objects into this editing context. I create an array of global ID's of one type of fetched object and return this array from performAction(). pageForResult() returns this global ID array to the result page which converts them to faults in the main thread editing context. However, these objects have null properties, so when they are referenced, they are refetched which defeats the entire purpose of the WOLongResponsePage.
What am I doing wrong to cause this refetch? Do I need to return global ID's of all 15,000 objects to prevent them from being refetched even though they are all related?
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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