I think the deeper problem is the nature of ajax. The ajax request sends only the info it thinks necessary and is expecting certain result info. But if the request is from an old state against a new state there is no way it can work properly in general. What should happen is a result that says something about a timeout/incompatible state and gets the user to go back to a clean state. What I might be able to do is to turn the jijx report about the error and the html 402 response into an out-of-synch response to the ajax request that result in proper notification to the user.
On Sat, Jan 15, 2011 at 5:55 PM, Raul Miller <[email protected]> wrote: > On Sat, Jan 15, 2011 at 2:24 PM, Eric Iverson <[email protected]> > wrote: > > The problem you show with jal is an example of a more general problem > with > > old browser pages (old in the sense of either from an previous state of > the > > current jhs task or from a previous jhs task). I don't know how to fix > this > > and at this stage it is beyond the scope of the current release. > > I can think of two fixes. > > One: have stub bootstrap loaders for all actions, which know how to > load and hand off to their downstream counterparts. > > Two: prefix each action with a conditional load (something that does a > require, or whatever). > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
