From programmers point of view: James Wilson wrote:
> I have to senerios in mind -- what do you > guys think? > > Case 1: > You have a servlet engine on box A and > a servlet engine on box B. Then you create > a HTTP POST/GET connection from box A to box B. You must provide de/marshalling of requests/responses on your own with all implications. => You have to create your own framwork apart from your intended functionality. => More work compared to case 2 > > > Case 2: > You have a servlet engine on box A and > a RMI server on box B. Then you communicate > from the box A to the RMI server via RMI. > You simply define a interface, and then program your client/server functionality against this interface Because de/marshalling stubs and skeletons are tool generated, you only program functionality. => Less work compared to case 1 BTW: You may use soap as third alternative. But soap was designed for web services and that should be kept in mind. Peter Huber (IT Consultant) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Gauss Interprise Consulting AG Gesch�ftsstelle M�nchen Witneystr.1 D-82008 Unterhaching Telefon: +49-89-66561 - 128 Fax: +49-89-66561 - 199 e-mail: mailto:[EMAIL PROTECTED] Germany Web: http://www.gi-consulting.de ___________________________________________________________________________ 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
