Do whatever makes sense in your system first. If you're concerned about performance then you need to benchmark your options and get real data.
David
From: "Andy Kriger" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: question about Action overhead and best practice
Date: Fri, 25 Oct 2002 10:14:48 -0400
I have the current setup
JSP (behind an Action) <-> Action -> JSP (behind an Action)
The Action in the middle does several things, none particularly large (let's
say 10 lines of code each). It would probably be cleaner design to separate
the tasks into separate actions. However, I am curious about the overhead
attached to this within the Struts system.
Right now there is one Action called which either returns to the first JSP
or continues to the second JSP. Breaking that Action up increases the number
of messges passed around in the system, however, I don't know how Struts
works under-the-hood, so I don't know how much extra Struts work would take
place. Can anyone tell me how much extra activity is generated by each
additional Action?
thx
andy
--
To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
_________________________________________________________________
Broadband? Dial-up? Get reliable MSN Internet Access. http://resourcecenter.msn.com/access/plans/default.asp
--
To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
