Date: Thu, 22 Aug 2002 02:44:36 +0100 From: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> To: Dylan Carlson <absinthe@pobox.com> Cc: freebsd-java@freebsd.org Subject: Re: Good distributed app technique for Java FreeBSD? Message-ID: <20020822014436.GC16407@dogma.freebsd-uk.eu.org> In-Reply-To: <200208212140.54805.absinthe@pobox.com> References: <20020822012251.GA16283@dogma.freebsd-uk.eu.org> <200208212133.09593.absinthe@pobox.com> <20020822013623.GA16407@dogma.freebsd-uk.eu.org> <200208212140.54805.absinthe@pobox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
| > So you used a client that talked to servlets via HTTP that talked to | > components via RMI? | | Yup, exactly. In this particular application used ICE as the protocol between | the client and the servlet. The servlet talks to other servlets via RMI. | Oracle backend. All the front-end machines FreeBSD 4.6 with the native SDK | build. <snip> | Don't know much in the area of EJB myself. But I do know that going the EJB | route is almost an entirely different school of thought. Interesting. I thought servlets were best for dealing with http requests, yet you were using them as components? Since they were also interfacing with a DB on the backend, how is this so different from EJB components? jm -- My other computer is your Windows box. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020822014436.GC16407>