Hi,
I think he is referring to continuations.
They do not persist forever, and therefore the page the URL points to does not persist forever.
The point is that continuations allow a way of traversing between various mid-way states, there should be little use in saving a URL to an intermittant state. If you use continuations to traverse a set of forms, the continuation represents some intermediate state. When you finish that set of forms, you should be able to redirect to a page with a "static" URL to display that data. This "static" URL should be used to direct people to specific information. I enclose the word static in quotaion marks because a URL could still look like: http://my.host/path/page?foo=2 in order to find out information about the third foo.
You can still save continuation objects in a database for later retrieval if required, but I wouldn't recommend storing them forever - using them as intermediate data storage when traversing pages is their intent, directing *somebody else* to a half filled in form (which spans multiple pages) should have very limited use.
Ben
----- Original Message ----- From: "Derek Hohls" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 10, 2004 1:57 PM
Subject: Re: when to use XSP ?
Stavros
I really don't understand what you're saying; but Cocoon is more than big enough to accomodate our different ways of doing things ;-)
Derek
[EMAIL PROTECTED] 2004/09/10 02:47:53 PM >>>On Fri, 10 Sep 2004, Derek Hohls wrote:
Derek
i like flow and i use it but in simple cases it no pretty to have this GUID in url and in a site completlty drived by flow you are not able to copy-paste url to add it in a email
ps I notice that i'm not complain about flow
-- stavros
isStavros
What do you mean when you say "flow destroys URL"; the flow is simply there to route the application process from one URL to another; you could replicate it in some ways by writing custom actions but that approach is far more tedious and less maintainable.
See also: http://wiki.apache.org/cocoon/MVC
>>> [EMAIL PROTECTED] 2004/09/10 02:32:46 PM >>> On Fri, 10 Sep 2004, [EMAIL PROTECTED] wrote:
after sqltransformer the only way to generate XML from sql queries---------------------------------------------------------------------xsp
this is very helpfull is you have to do with select queries
an other point is that flow is great for web apps but "destroy" URL.
in simple case is better to have a clean url
-- stavros
> I've created a simple blog with cocoon > It's only using Flow, XML, and stylesheet only > no XSP at all > > The question is: > When should we use XSP (best time to use XSP)? > >
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
