the @Meta("tapestry.persistence-strategy=X") works beautifully... no more
sessions till logged in.
On Mon, Apr 7, 2008 at 7:14 PM, Robert Zeigler <[EMAIL PROTECTED]> wrote:
>
> On Apr 7, 2008, at 4/712:53 PM , Fernando Padilla wrote:
>
> > so.. the "client" strategy stores it in a cookie?
> >
> >
> Client strategy stores it in the url.
> Not sure how that would play out for myspace, etc.
>
> Robert
>
>
>
> Yeah, I don't really have access to those either :)
> >
> > ps - This is for integration with GoogleGadgets/OpenSocial/MySpace/Hi5.
> > So it's basically a portlet hosted on a different site. And the requests
> > to my server are being proxied by MySpace/Hi5 so we don't have access to
> > cookies from the client side..
> >
> > pps - I am using Zones and Form/Zones, so I'm rendering on the same
> > request as the submit, and at first glance that seems to be working. I just
> > wanted to make sure "persist"/"session" requirement wasn't going to bite me
> > later..
> >
> > ppps - So if we're doing the render on the same request as submit, we
> > don't really have to store the Validation object in the session right?
> >
> > Howard Lewis Ship wrote:
> >
> > > The approach I would take would be to configure the Form to store its
> > > persistent fields on the client, rather than in the Session.
> > > On your PAGE, you can add a @Meta annotation for this:
> > > @Meta("tapestry.persistence-strategy=client")
> > > public class MyPage { ...
> > > This sets the default persistence strategy for the entire page to be
> > > "client". Since in most cases, @Persist is used without a specific
> > > strategy, even nested components (such as Form) will inherit a default
> > > persistent strategy from their container.
> > > I haven't tried this yet myself ... give it a try and report back!
> > > On Mon, Apr 7, 2008 at 5:05 AM, Peter Stavrinides
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > > > If I understand correctly you need to pass data completely
> > > > independent of
> > > > session state... then your options are hidden form fields, and or
> > > > URL
> > > > parameters. Of course then you would have to reinitialize your
> > > > properties
> > > > manually after posting, which is not such big a deal!
> > > >
> > > >
> > > >
> > > > Fernando Padilla wrote:
> > > >
> > > > I have a requirement to not depend on HttpSession, but the Form
> > > > > component
> > > > >
> > > > has a @Persist field that Tapestry wants to store in a session.
> > > > What are
> > > > some options to avoid this?
> > > >
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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]
> > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > 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]
>
>
