enius" <[EMAIL PROTECTED]>
Sent: Monday, May 19, 2008 7:18 AM
To:
Subject: Re: Page pooling (for stateless pages)
On Sun, May 18, 2008 at 11:04 PM, James Carman
<[EMAIL PROTECTED]> wrote:
stateless != static, though
If you cache the results of a stateless page, you could show
On Sun, May 18, 2008 at 11:04 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> stateless != static, though
>
> If you cache the results of a stateless page, you could show stale
> information from the database, correct?
True, so it depends on your use case. And obviously it wouldn't work
for form pro
stateless != static, though
If you cache the results of a stateless page, you could show stale
information from the database, correct?
On Mon, May 19, 2008 at 1:18 AM, Erik van Oosten <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I think it would probably make more sense to cache the /result/ of statel
> I think it would probably make more sense to cache the /result/ of stateless
> pages.
Yeah, that might make quite the difference. The best place for that
would be a filter, probably defined before the Wicket filter. Tons of
different options as well though. And definitively something I would
onl
Hello,
I think it would probably make more sense to cache the /result/ of
stateless pages.
Regards,
Erik.
Joel Halbert wrote:
Hi,
I was wondering whether it was possible to implement "pooling" of stateless pages? Possibly using a custom PageMap implementation?
Although newer JVM's a
-------
>> From: "Eelco Hillenius" <[EMAIL PROTECTED]>
>> Sent: Sunday, May 18, 2008 5:58 PM
>> To:
>> Subject: Re: Page pooling (for stateless pages)
>>
>> I was wondering whether it was possible to implement "pooling" of
>>
ot; <[EMAIL PROTECTED]>
> Sent: Sunday, May 18, 2008 5:58 PM
> To:
> Subject: Re: Page pooling (for stateless pages)
>
> I was wondering whether it was possible to implement "pooling" of
>>> stateless pages? Possibly using a custom PageMap implementatio
any metrics that we produce.
Thx,
Joel
--
From: "Eelco Hillenius" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 5:58 PM
To:
Subject: Re: Page pooling (for stateless pages)
I was wondering whether it was possible to implem
> I was wondering whether it was possible to implement "pooling" of stateless
> pages? Possibly using a custom PageMap implementation?
I think you can just implement the pooling mechanism yourself, and
provide a custom version of IPageFactory (which is to be set in
session settings).
> Although
On Sun, May 18, 2008 at 9:47 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> do you have a benchmark that shows that pooling is indeed faster?
>
> servlets are pooled because they may require heavy initialization.
> wicket pages are much more lightweight in comparison.
And, the more heavyweight you
ter
> scalability.
>
> Rgs,
> Joel
>
> --
> From: "Johan Compagner" <[EMAIL PROTECTED]>
> Sent: Sunday, May 18, 2008 12:27 PM
> To:
> Subject: Re: Page pooling (for stateless pages)
>
>> For stateless
t; --------------
>> From: "Johan Compagner" <[EMAIL PROTECTED]>
>> Sent: Sunday, May 18, 2008 12:27 PM
>> To:
>> Subject: Re: Page pooling (for stateless pages)
>>
>>
>>
>> > For stateless pages
java servlet containers do with stateless
> Servlets.
> It is also the a technique used by Tapestry 5 to achieve greater
> scalability.
>
> Rgs,
> Joel
>
> --
> From: "Johan Compagner" <[EMAIL PROTECTED]>
>
nt, so long as they
are all young gen objects. And with parallel gc this should result in
minimal effect on an application.
--
From: "Martijn Dashorst" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:42 PM
To:
Subject: Re: Page pool
s
> Servlets.
> It is also the a technique used by Tapestry 5 to achieve greater
> scalability.
>
> Rgs,
> Joel
>
> --
> From: "Johan Compagner" <[EMAIL PROTECTED]>
> Sent: Sunday, May 18, 2008 12:2
be implemented.
I noted that Tapestry 5 has chosen to implement stateless pages and pooling
of these by default.
--
From: "Matej Knopp" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:25 PM
To:
Subject: Re: Page pooling (for
ity.
Rgs,
Joel
--
From: "Johan Compagner" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:27 PM
To:
Subject: Re: Page pooling (for stateless pages)
For stateless pages??
The whole point of stateless is that they arent kept in
For stateless pages??
The whole point of stateless is that they arent kept in the session/memory.
And pooling pages is not really what you want any way, you can only
pool then for a single user/sessiion so you would have a pool for
every session.
And when do you decide to return a pooled page?
O
For stateless pages??
The whole point of stateless is that they arent kept in the session/memory.
And pooling pages is not really what you want any way, you can only
pool then for a single user/sessiion so you would have a pool for
every session.
And when do you decide to return a pooled page?
O
Hi,
first of all, I don't really think it's worth pooling pages. I can't
imagine that page instance creation would have that much overhead.
Also stateless pages doesn't mean they don't contain any state. The
page is stateless because it's not kept between requests, but during
request there's lot
Hi,
I was wondering whether it was possible to implement "pooling" of stateless
pages? Possibly using a custom PageMap implementation?
Although newer JVM's are good at performing GC, pooling is a reasonable
additional technique to use for achieving that extra bit of scalability.
If anyone has
21 matches
Mail list logo
