question about Action overhead and best practice
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
Re: question about Action overhead and best practice
I see nothing wrong with an Action returning a different ActionForward depending on system conditions. If you break it up you won't notice any performance difference. Struts only creates one object per Action, effectively making Actions Singletons, so the memory requirement is very small. Struts will have to choose between more Actions but that decision is extremely fast. 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
question about Action overhead and best practice
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
