Em Wed, 06 Jan 2010 13:36:31 -0200, Jim O'Callaghan
jc1000...@yahoo.co.uk escreveu:
Thanks for the responses Thiago.
You're welcome!
I'll have a look at the
LinkCreationListener you suggested in your other email. Regarding the
response below, does the approach not make an assumption that
I agree that one should try to defer session creation as long as possible.
But as soon as there is some state to persist, you shouldn't hesitate to use
sessions.
Session replication isn't necessarily a heavy thing.
Have a look at Terracotta, which shines at making web session replication
scale
Hi,
Can anyone advise on the preferred way of persisting state between pages
without using HTTP Session? PageActivationContext using Object[] looks
promising but I don't want long urls (from serialized objects) and there is
more data to share than a defined number of keys - I'm looking for
Cookies come to mind, would that be an option?
On Wed, Jan 6, 2010 at 2:16 PM, Jim O'Callaghan jc1000...@yahoo.co.uk wrote:
Hi,
Can anyone advise on the preferred way of persisting state between pages
without using HTTP Session? PageActivationContext using Object[] looks
promising but I
Use setters and the @InjectPage annotation.
@InjectPage private MyPage resultpage;
Object onActionFromSomeComponent()
{
resultpage.setSomething(something);
return resultpage;
}
Uli
On 06.01.2010 14:16 schrieb Jim O'Callaghan:
Hi,
Can anyone advise on the preferred way of persisting
the relevant object(s)
using Request parameters rather than the querystring / url - thanks.
Regards,
Jim.
-Original Message-
From: Lutz Hühnken [mailto:lh.tapestry.l...@googlemail.com]
Sent: 06 January 2010 13:50
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Cookies
January 2010 13:58
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Use setters and the @InjectPage annotation.
@InjectPage private MyPage resultpage;
Object onActionFromSomeComponent()
{
resultpage.setSomething(something);
return resultpage;
}
Uli
On 06.01.2010 14
Em Wed, 06 Jan 2010 11:16:23 -0200, Jim O'Callaghan
jc1000...@yahoo.co.uk escreveu:
Hi,
Hi!
Can anyone advise on the preferred way of persisting state between pages
without using HTTP Session? PageActivationContext using Object[] looks
promising but I don't want long urls (from
Em Wed, 06 Jan 2010 12:04:44 -0200, Jim O'Callaghan
jc1000...@yahoo.co.uk escreveu:
What I'm after is something akin to PageActivationContext but that
passes the relevant object(s) using Request parameters rather than the
querystring / url - thanks.
Take a look at the
...@spielviel.de]
Sent: 06 January 2010 13:58
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Use setters and the @InjectPage annotation.
@InjectPage private MyPage resultpage;
Object onActionFromSomeComponent()
{
resultpage.setSomething(something);
return resultpage;
}
Uli
[mailto:lh.tapestry.l...@googlemail.com]
Sent: 06 January 2010 13:50
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Cookies come to mind, would that be an option?
On Wed, Jan 6, 2010 at 2:16 PM, Jim O'Callaghan jc1000...@yahoo.co.uk wrote:
Hi,
Can anyone advise
this.
Regards,
Jim.
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 06 January 2010 14:40
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Em Wed, 06 Jan 2010 11:16:23 -0200, Jim O'Callaghan
jc1000...@yahoo.co.uk escreveu:
Hi
]
Sent: 06 January 2010 15:06
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
I forgot that in order to store the object until the result page is being
rendered, you'll need to
somehow persist it. That would happen in the session again. So this is not
an option for you
minimising the
amount of data held. Thanks for your contributions.
Regards,
Jim.
-Original Message-
From: Lutz Hühnken [mailto:lh.tapestry.l...@googlemail.com]
Sent: 06 January 2010 15:26
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
I see. There wouldn't be much
[mailto:u...@spielviel.de]
Sent: 06 January 2010 13:58
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Use setters and the @InjectPage annotation.
@InjectPage private MyPage resultpage;
Object onActionFromSomeComponent()
{
resultpage.setSomething(something);
return
Jim,
You still have some different options to pursue in a cluster..
- sticky sessions, so that requests of the same user will go to the
same server in the cluster. Good for load balancing, but if a server
fails, the users of that server will loose their session.
- session replication in the
Ulrich, Lutz,
Thanks for the very informative replies. Hopefully they will be useful to
others also.
Regards,
Jim.
-Original Message-
From: Lutz Hühnken [mailto:lh.tapestry.l...@googlemail.com]
Sent: 06 January 2010 15:56
To: Tapestry users
Subject: Re: Persisting state without HTTP
Thanks for the details Howard - I'll keep an eye on this one.
Regards,
Jim.
-Original Message-
From: Howard Lewis Ship [mailto:hls...@gmail.com]
Sent: 06 January 2010 18:44
To: Tapestry users
Subject: Re: Persisting state without HTTP Session
Something I'm hoping to put together
18 matches
Mail list logo
