----- Original Message -----
From: Milt Epstein <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 11, 2000 6:46 PM
Subject: Re: How to design a efficient program?
> Another rule of thumb for servlets is that you should think of them as
> a web gateway to an application, and only things that are part of that
> request/response transaction should go there -- and anything that's
> more inherently part of the application shouldn't go there.
This was the information I needed. At the moment we use lots of large
servlets to handle doGet *and* doPost in one servlet. As I was comparing log
files, I noticed that the servlets are kept in memory until they are used
again. Therefor I started to wonder if it's practical to have them large and
multi-functional (and of course because that way of programming isn't really
Object Orientated). At the moment we are revising the whole program to work
with some small servlets and Objects (like
seperate-Class-files-with-a-whole-range-of-methods-kind of objects). This
confirms my suspicion that that's indeed the most efficient way to do it.
Thanks!
Kind regards,
Met vriendelijke groet,
Tim Stoop
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
