Kuhnert" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Monday, February 12, 2007 4:45 PM
Subject: Re: TAPESTRY-825 ASO in cookie
> It is hard to say. What version of Tapestry are you working with?
>
> Not my business to say, but I'd be more than a little wor
pointer to the Storage API, I have to take a closer look at
that.
Regards,
Manri
- Original Message -
From: "Jesse Kuhnert" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Monday, February 12, 2007 4:45 PM
Subject: Re: TAPESTRY-825 ASO in cookie
It is ha
p.s. Not to say that this isn't still possible. I think more and more
the new "way" of carrying state around on the client side (a necessity
for high load sites) will be more use of the native (or virtual with
Dojo ) storage provider API's available in some browsers. (Dojo uses
the native firefox
It is hard to say. What version of Tapestry are you working with?
Not my business to say, but I'd be more than a little worried about
trying to store so much state in a cookie object. Despite the relative
ease with which different API's make it possible to muck around with
them most people don't
Hi Tapestry users,
I am trying to store an ASO in a cookie. I have read previous posts about
problems when the cookie is written and that the issue was fixed, but I still
seem to have problems.
Somehow the store() method of my CookieScopeManager does not write anything to
the cookie at all.
I
