Tapestry could add an option to NOT encode the session id into URLs, with the caveat that clients with cookies disabled would see degraded or non-functional behavior. Anyway, it's one of the advantages of having all URLs generated through a single piece of code.
On Wed, Mar 5, 2008 at 11:42 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: > Hi, > > I've been running a production application with a servlet filter that > strips the jsessionid for a couple of weeks now and everything's been > fine so far. > > -Filip > > Daniel Leffel skrev: > > > > Hi, > > We're in the process of developing a webapp using T5. The site leverages > > session persistence on many pages, including a number of pages important > for > > the natural search content. It seems to us that levering a filter to strip > > the jessionid from non-cookie enabled user agents would be an effective way > > to keep jsessionids from popping up in the url. Other than insuring all > > pages gracefully handle sessions which are effectively stateless (from > > non-cookied enabled user agents), are there any other concerns we should be > > thinking about? > > > > Danny > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
