Can't you just use cookie.setDomain()? Set both cookies to the same domain. Doesn't sound Tapestry- or javascript-related.
On Wed, Jun 3, 2009 at 9:37 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Wed, 03 Jun 2009 21:02:06 -0300, Angelo Chen < > angelochen...@yahoo.com.hk> escreveu: > > Hi, >> > > Hi! > > My App has a url: http://example.com, then user can also visit it >> http://www.example.com. I use T5's cookie service to write some visitor's >> related info back to the visitor's browser. the problem now is, if user >> uses http://example.com, cookie will be under example.com, if he uses >> www.example.com, then the cookie will be under www.example.com, the two >> now looks different from each other as far as cookie is concerned, any >> thoughts on keeping only one set of cookie for two urls(http:// or www.)? >> Thanks, >> > > This is mostly Javascript related than Tapestry related, but I think one > elegant solution would be to use Tapestry to redirect all requests to the > same domain (www.example.com to example.com, for example). > > Don't forget that, in Tapestry, many problems can be solved using a request > filter or a dispatcher. ;) > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
