Re: Backtracking detection in a long response page
Re: Backtracking detection in a long response page
- Subject: Re: Backtracking detection in a long response page
- From: Pascal Robert <email@hidden>
- Date: Tue, 8 Jun 2010 13:58:20 -0400
This is not what's happening in my testing so far. With Firefox on
Windows, if I backtrack on the long response page, I get back on the
page where the long response page was called, and if the user call the
long response page again, the code in performAction is performed
again, which create havoc.
Same thing if the long response is done and I land on the page
specified in pageForResult, if I backtrack, I'm getting back to the
page that called the long response page.
How is that a problem? The only thing the users *might* see while
backtracking is "50% done" followed by "45% done" followed by "51%
done" after the next refresh?
Cheers, Anjo
Am 08.06.2010 um 19:26 schrieb Pascal Robert:
BTW, how I found out that users are backtracking is because I saw
this in Apache logs :
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
28.WOMetaRefresh
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
29.WOMetaRefresh
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
29.WOMetaRefresh
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
28.WOMetaRefresh
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
32.WOMetaRefresh
So the context ID was on 28, 29, went back to 28 and moved to 32.
Look like this :
/cgi-bin/WebObjects/Depot.woa/1/wo/a5wsIRHrgb2vaKM3n3WaHg/
9.WOMetaRefresh
What is the URL for the long response page (the URL they are
backtracking to)? Which path is it taking through that method?
Chuck
On Jun 8, 2010, at 8:04 AM, Pascal Robert wrote:
This is so great. Deadlocks are now gone in our app, but I
noticed that some users are using the back button in the app. So
I looked at ERXSession.didBacktrack(), and this is working fine
for "normal" components, eg if I backtrack on a normal
component, didBacktrack() returns true.
Problem is that most backtracking that I found was in our long
response page, and back tracking doesn't seem to be detected in
there. didBacktrack is always false, either in invokeAction(),
appendToResponse() or sleep(). I looked at didBacktrack() source
and I don't see why it won't work on a long response page.
Any tips on this?
----
Pascal Robert
email@hidden
AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
WO Community profile : http://wocommunity.org/page/member?name=probert
_______________________________________________
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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@krank.net
This email sent to email@hidden
_______________________________________________
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
_______________________________________________
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