From owner-freebsd-java Wed Aug 21 18:23: 4 2002 Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D0BF37B405 for ; Wed, 21 Aug 2002 18:23:01 -0700 (PDT) Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6813C43E6A for ; Wed, 21 Aug 2002 18:23:00 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #7) id 17hggW-000EM2-00 for freebsd-java@freebsd.org; Thu, 22 Aug 2002 02:22:52 +0100 Received: from dogma.freebsd-uk.eu.org (localhost [127.0.0.1]) by dogma.freebsd-uk.eu.org (8.12.3/8.11.1) with ESMTP id g7M1Mp3H016315 for ; Thu, 22 Aug 2002 02:22:51 +0100 (BST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.12.3/8.12.3/Submit) id g7M1MpCo016314 for freebsd-java@freebsd.org; Thu, 22 Aug 2002 02:22:51 +0100 (BST) Date: Thu, 22 Aug 2002 02:22:51 +0100 From: Jonathon McKitrick To: freebsd-java@freebsd.org Subject: Good distributed app technique for Java FreeBSD? Message-ID: <20020822012251.GA16283@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Scanner: exiscan *17hggW-000EM2-00*kujgW8mu3mw* (Manchester Computing, University of Manchester) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello all, I'm trying my hand at some ideas for a distributed Java application. At the moment, I'm considering a few possible solutions, but I'm not sure which would would best on FreeBSD. Here is a brief example of what I would like to try as a proof of concepts, based on a possible scenario: >>> We have data acquisition instruments with a controlling host computer. Imagine these in a lab, connected to the network. Somewhere else in the building, or perhaps even outside on the internet, is a server that has the proprietary processing algorithms that I could charge for by use. This web service would be exposed to all customers, regardless of platform. Other companies could even publish similar services as well. Now, imagine a scientist in their office in the first building. They have an applet which connects to the component controlling the instrument, gets the data, and sends it to the outside service for processing. <<< Would it make sense to make the instrument controller an EJB? How about the processing web service? Or should one or both be servlets? Would Jini be better here, or maybe just plain RMI? I'm trying to balance flexibility with performance. At this point, I'm not going to worry too much about the size of the data being transferred, though that could become an issue for large data acquisitions. 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