Stateless pages and performance

[Martijn Lindhout <ml...@jointeffort.nl>]

Hi guys,

In the release notes, I read: "stateless pages and components for those
parts of your application that needs to scale to extremely large numbers of
users".

Does somebody use this feature or is it somewhere documented? What do I have
to do and what are the differences from a 'normal' wicket app?

Regards,

-- 
Martijn Lindhout
JointEffort IT Services
http://www.jointeffort.nl
mlindhout@jointeffort.nl
+31 (0)6 18 47 25 29

Re: Stateless pages and performance

[Eelco Hillenius <ee...@gmail.com>]

On Jan 19, 2008 5:18 AM, Martijn Lindhout <ml...@jointeffort.nl> wrote:
> Hi guys,
>
> In the release notes, I read: "stateless pages and components for those
> parts of your application that needs to scale to extremely large numbers of
> users".
>
> Does somebody use this feature or is it somewhere documented? What do I have
> to do and what are the differences from a 'normal' wicket app?

Stateless pages can be a good option for things like public home pages
etc; pages where you don't have a crazy amount of functionality, but
that get hit hard. More interesting imho than the scalability argument
is that such stateless pages are always bookmarkable. This makes them
very useful for e.g. login pages, where you can expect clients to
directly go to, or maybe have in the background for an extended time
before actually using it.

Read about it here:
http://cwiki.apache.org/WICKET/stateless-pages.html and take a look at
org.apache.wicket.examples.stateless in wicket-examples.

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Stateless pages and performance

[Jonathan Locke <jo...@gmail.com>]

sorry, can't find it.  maybe someone downloaded it and could post it to the
list.


Uwe Schäfer wrote:
> 
> Jonathan Locke schrieb:
> 
> hi Jonathan
>> Until you've got a handle on your scaling problem (and it
>> probably is that and not a performance problem) and you know what needs
>> to
>> be tuned, the best policy is probably to just build something simply and
>> quickly in order to discover if you even have a problem that requires
>> this
>> solution.
>>   
> talking about scalability, you posted a CachedPanel on your blog once. 
> unfortunately it seems to be gone. is this still floating around anywhere?
> 
> thx uwe
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Stateless-pages-and-performance-tp14970238p14983297.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Stateless pages and performance

[Uwe Schäfer <sc...@thomas-daily.de>]

Jonathan Locke schrieb:

hi Jonathan
> Until you've got a handle on your scaling problem (and it
> probably is that and not a performance problem) and you know what needs to
> be tuned, the best policy is probably to just build something simply and
> quickly in order to discover if you even have a problem that requires this
> solution.
>   
talking about scalability, you posted a CachedPanel on your blog once. 
unfortunately it seems to be gone. is this still floating around anywhere?

thx uwe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Stateless pages and performance

[Jonathan Locke <jo...@gmail.com>]

As always, the caveat is that you should avoid premature optimization like
the plague. Until you've got a handle on your scaling problem (and it
probably is that and not a performance problem) and you know what needs to
be tuned, the best policy is probably to just build something simply and
quickly in order to discover if you even have a problem that requires this
solution.


Martijn Lindhout wrote:
> 
> Hi guys,
> 
> In the release notes, I read: "stateless pages and components for those
> parts of your application that needs to scale to extremely large numbers
> of
> users".
> 
> Does somebody use this feature or is it somewhere documented? What do I
> have
> to do and what are the differences from a 'normal' wicket app?
> 
> Regards,
> 
> -- 
> Martijn Lindhout
> JointEffort IT Services
> http://www.jointeffort.nl
> mlindhout@jointeffort.nl
> +31 (0)6 18 47 25 29
> 
> 

-- 
View this message in context: http://www.nabble.com/Stateless-pages-and-performance-tp14970238p14975570.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org