• 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
trying to isolate bug involving URL caching
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

trying to isolate bug involving URL caching


  • Subject: trying to isolate bug involving URL caching
  • From: Jonathan Rochkind <email@hidden>
  • Date: Thu, 04 Sep 2003 14:23:52 -0500

I am attempting to isolate a bug in WO framework code, but having some trouble.

The documentation for WOApplication pageRefreshOnBacktrackEnabled says:

"When this flag is turned on and a request corresponding to a client backtrack occurs, the retrieved page will only be asked to regenerate its response. The first two phases of a normal request-response loop (value extraction from the request and action invocation) do not occur."

Note that by defualt, this flag is turned on.

I have noticed in my applications some instances where this is NOT true. If a user clicks on a link, and it takes a while for the response to be returned (application load, slow network, whatever), and then the user clicks on that same link _again_----resulting in the same URL being sent to the application----in _some_ cases the action is invoked twice.

I realize that this isn't exactly a 'request corresponding to a client backtrack', but to the application it's much the same. When I try to reproduce this behavior in a simple test application---I can't. The action is not invoked twice, and indeed, just as the documentation says, the originally produced page is simply asked to regenerate it's response.

However, in some cases in my actual complex applications, the action is invoked twice (but never more than twice, no matter how many times the user clicks on the link). It's easy enough for me to reproduce this in my actual complex application, but when I try to boil it down to a simple test case to give Apple.... I can't get it to happen. So I'm not sure what's going on in my app to cause this.

Has anyone else investigated this at all?

--Jonathan
_______________________________________________
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: best practice(s) for validating properties
  • Next by Date: Amateur's query
  • Previous by thread: Re: best practice(s) for validating properties.. and the answer is...
  • Next by thread: Re: trying to isolate bug involving URL caching
  • Index(es):
    • Date
    • Thread