From fadushin@syr.edu  Tue Apr  4 01:22:37 2000
Received: from fadushin.ne.mediaone.net (fadushin.ne.mediaone.net [24.218.120.90])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id BAA19824
	for <prolog@swi.psy.uva.nl>; Tue, 4 Apr 2000 01:22:36 +0200 (MET DST)
From: fadushin@syr.edu
Received: from fadushin.ne.mediaone.net (fadushin.ne.mediaone.net [24.218.120.90])
	by fadushin.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id TAA29830;
	Mon, 3 Apr 2000 19:32:20 -0400
Date: Mon, 3 Apr 2000 19:32:20 -0400 (EDT)
X-Sender: fadushin@fadushin.ne.mediaone.net
Reply-To: Fred Dushin <fadushin@syr.edu>
To: Paul Singleton <p.singleton@keele.ac.uk>
cc: SWI Prolog <prolog@swi.psy.uva.nl>
Subject: Re: CGI with SWI-Prolog
In-Reply-To: <38E8D195.25DFBD76@keele.ac.uk>
Message-ID: <Pine.LNX.4.10.10004031928210.29823-100000@fadushin.ne.mediaone.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> [potential disadvantage of the JPL approach: the Java VM shares
> memory with the JPL library, the Prolog VM and any foreign code
> loaded by it, and is thus vulnerable to corruption; i.e. commercial
> or corporate Web servers may reasonably refuse to host servlets
> which load Java "native methods"]

There may also be threading issues (though JPL should be thread safe).
I believe there are some contortions you can go through with Apache
J-serv in order to get your web server to host multiple JVMs, though,
if you're concerned about performance/load balancing.  

I agree though, servelts are the way to go, with or without JPL.

/Fred

