I'm using the last approach, and we don't have any problems. I don't know if this will work if a user calls the page from 2 different pages in 2 different tabs. Maybe on the returning, one of them will be lost. Which of these other approaches will solve this problem?
On Fri, Jan 23, 2009 at 9:04 AM, Lance Java <lance.j...@googlemail.com>wrote: > 1 more suggestion: > A hidden "returnPage" field on each of referring pages and the referring > pages POST to the multiple entry page. > > 2009/1/23 Peter Stavrinides <p.stavrini...@albourne.com> > > > Hi everyone, > > > > I have a page with multiple entry points, when a user is done editing I > > want to return them to their previous page, there are a couple of ways of > > doing this I guess: > > - JavaScript (not so keen on this, I prefer a server side redirect) > > - Using the HTTP referer header of the Request service (I am thinking of > > using this, not sure what the drawbacks could be?) > > - ASO (hmmm not sure about the multiple window thing) > > - onActivate (don't want the callback URL to appear in the address bar) > > - Set a property on the page before calling onActivate (this could also > > work, of course it limits me to internal URL's over the referer > approach... > > but thats probably also okay though) > > > > I would like to know if there is any possibility that the referer might > not > > be set correctly under any circumstances etc... or if there is a better > way > > to call back a previous page/URL. > > > > Thanks, > > Peter > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > -- Atenciosamente, Marcelo Lotif Programador Java e Tapestry FIEC - Federação das Indústrias do Estado do Ceará (85) 3421-5910
