I've never considered nor heard of combining applet and servlet classes. Not only are you violating functional separation (decoupling), disregarding every accepted design pattern known, but are burdening the client with server code and vice-versa (though the latter's performance impact would be minimal). You can find details of the rationale for separating functionality in almost any publication on client/server or n-tier technology, or the Model-View-Controller design pattern (Sun's implementation DP). Cheers! Mark ----- Original Message ----- From: "[Steven Shaw]" <[EMAIL PROTECTED]> Sent: Tuesday, May 29, 2001 12:53 PM > Is it wise ( or neccessary ) to separate Applet classes from servlet > classes? Can this be answered in detail from some publication? > Thank you, > > -Steven Shaw _________________________________________________________________ __________ > 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 > ___________________________________________________________________________ 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
