[Note, I tried to send this yesterday 6/17, but it never showed up on the list. Are others having their posts disappear?]
Thank you for a great introduction to the concept of the flowmap! On Sun, 16 Jun 2002, Stefano Mazzocchi wrote: [snip] > 2) the concept of continuations is not transparent, there is concern > overlap between the view designers and the sitemap managers since the > view designers must be aware of the URI location of the > continuation-decoding URI. > > [NOTE: it is *not* required that you use continuations for your flow > logic, you can use whatever means you have to control state as you did > previously, such as REST-like passing style, sessions or cookies] What if continuations encoded in the uri were as transparent as they are with servlet sessions? For example, there could be a encodeContinuationURL(...) method in the environment interface/impls that transparently encode the continuation id and return an encoded url. Similarly, there would be a getContination() method that would return the continuation id of the request, or some undefined value (e.g. null) if no continuation is associated with the request. Most servlet implementations make use of the path parameter component of a URI to encode session ids so as not to interfere with request parameters, e.g. "/context/path?param1=value1" becomes "/context/path;j-session-id=1234?param1=value1". A similar approach could be used to implement the encodeContinuationURL(...) method. This makes the continuation id orthogonal to the request URI. Regards, --mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
