With an application like this, wouldn't the critical path (in terms of any performance bottlenecks) be more along the lines of your database communications? I've been finding that any bottlenecks I've had regarding performance were almost always due to hitting the database in an inefficient manner. Of course, I haven't had an opportunity to design applications w/ Pete's size of a user base.
To answer the question specifically, I actually prefer to keep all database mgt, security mgt, and biz logic out of action classes. I tend to have 1 action class for any general area of functionality (ie UserAction for User adds, edits, deletes) and then use that Action class as a controller to some other class that directs the actual functionality. ----- Original Message ----- From: "Pete Serafin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 29, 2002 10:33 AM Subject: Design help needed for large scale app > I am in the design phase of an application that will need to handle > 100's and more likely 1000's of users simultaneously. The application > will consist of the typical create, edit, and retrieve functions for > information stored in a database. My question concerns how to design my > Action classes. While I usually place the hi level logic for inserts, > updates, and individual object retrieval in the same Action class, I was > thinking about breaking them out into 3 separate Action classes. The > logic being that an Action class is created on the stack for each user > that accesses that class, and the slimmer the class, the faster the > application and less memory used. Would it make sense to architect the > application this way, or is it more just a matter of style? Does anyone > have any ideas on this issue, or advice based on large scale > applications that you have developed? Thanks, > > Pete Serafin > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
