Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 42412 invoked by uid 500); 20 Jun 2002 00:02:47 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 42401 invoked from network); 20 Jun 2002 00:02:47 -0000 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Wed, 19 Jun 2002 17:02:53 -0700 Subject: Re: Continuation as cookie? (was RE: [RT] Flowmaps) From: Ovidiu Predescu To: Message-ID: In-Reply-To: <3D1031EF.2030901@anyware-tech.com> Mime-version: 1.0 X-url: http://www.geocities.com/SilliconValley/Monitor/7464/ Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On 6/19/02 12:25 AM, "Sylvain Wallez" wrote: > Vadim Gritsenko wrote: > >>> From: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com] >>> >>> page leads to a new continuation. This is how the infamous "back button" >>> problem is elegantly solved, and also how you can use what-if browsing >>> >>> >> >> I could imagine application which has one and only continuation per >> client. In this scenario, when client hits "Back" button, application >> shows to the user *same*, *current* page but not *previous* page. But is not the application that shows the page, it's the browser if it maintains them in a cache. The continuation id helps identifying the state of the program on the server side, but this gets transmitted only when you make a new request from an old page. >> If you add continuation persistence on server side... In *this* >> scenario, cookies *do* make sense. Don't you agree? > > Yes, cookies do make sense for this. But in that case, do you really > need continuations ? IIRC, Ovidiu already talked about this, but I don't > remember exactly what he said. > > Ovidiu, what's your opinion on the above ? The problem is that a cookie does not change when you hit the back button in your browser. An application could have many continuations, and each continuation will have its own id. Thus, each URL which generated for a continuation will be different than all others. Your browser will maintain the history of URLs, as opposed to the value of your cookies. A cookie has only one value, no matter what you do with your browser history. That's why you cannot use cookies to represent continuations. Greetings, -- Ovidiu Predescu http://www.geocities.com/SiliconValley/Monitor/7464/ (Apache, GNU, Emacs...) --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org