I don't think that page serialization is going to be your bottleneck.
I don't know what you're thinking when you say "large scale." Some
folks think "large scale" means two server and others think
Travelocity or Google. I developed a system in PHP that served about
20-50 pages per second. This was PHP 4. I don't know if things are
different now, but in PHP 4, the PHP module interpreted every PHP page
from scratch, loaded the session state from disk, rendered the page,
and wrote the session state back to disk, with every request. The
time required to serialize the session to the disk and read it back
every time was negligible.
I suggest you write your Wicket app first, then analyze the
performance and determine what you need to optimize. It almost
certainly won't be the serialization. It will be your own code:
mostly database access and synchronized blocks.
W
On Mar 12, 2009, at 11:52 PM, subbu_tce wrote:
Do we have any Clustering Solutions other than Terracotta that can
integrate
with Wicket to avoid serialization of pages to support development of
applications in a large scale?
Thanks,
Subbu.
--
View this message in context:
http://www.nabble.com/Large-Scale-Applications-using-Wicket-tp22489752p22489752.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
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]
