Well just a shot in the dark but maybe a slight speed up maybe achieved by pre-compiling jsps possibly.
On Fri, 23 Jul 2004 10:05:30 +0800, Koon Yue Lam <[EMAIL PROTECTED]> wrote: > Oh! thanks for all of these help ! > I don't expect over 10 mails in one night to this issue~~ > Maybe becasue the timezone because I am from Hong Kong, ^^ > > [About Struts] > After some testing, I prove myself wrong ! > The delay wasn't cause by Struts, it is cause by JSP instead. The > delay time is the time that use to compile and transform the JSP to > servlet, sorry for the silly question because I haven't read through > all the spec. ^^ > > [To HG] > I said the problem deal with cluster means: > assume we have 3 servers (S1, S2, S3) form a cluster and one Struts > plugins deal with home object caching (P1) > > when the application start up, P1 with get all home interfaces from > the cluster and also create all home objects and cache them. > > so if P1 get an object (O1) from S1 and cache it, this O1 is indeed an > instance created by S1 and if S1 go down, O1 would still reference to > S1 and become NULL > > The question comes to if i call some method to O1 at this time, will > the cluster manager redirect the request to another machine?? I don't > think it will hapen because you locally cache the object reference. > But if you get the home object from the JNDI tree again, I am sure the > cluster manager will preform a failover and redirect all request > target to S1 to another machine > > do I make any sense? > > great to have this disussion > > Regards > > --------------------------------------------------------------------- > 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]
