|
From: <php...@li...> - 2009-09-17 12:57:01
|
[Please excuse the delay] > Easier to handle is relative, no? May be. On Windows and Linux all you need to do is to start the graphical software installer and install tomcat. After that it runs as a standard system service. > Is it *bad* to run it standalone? Not at all. But it may not be as fast as a servlet back end with JAVA_PERSISTENT_SERVLET_CONNECTIONS set to true. The simple servlet engine built into JavaBridge.jar cannot handle persistent connections (it uses http/1.0, not http/1.1). But the standalone socket listener can use persistent connections: java -jar JavaBridge.jar INET_LOCAL:9267 And in your php script or in java.inc set JAVA_HOSTS to "127.0.0.1:9267" and JAVA_SERVLET to false. Regards, Jost Boekemeier On Sep 14, 2009 12:26 AM, <php...@li...> wrote: Easier to handle is relative, no? I have -0- experience running Java App Servers. This is why I run it standalone; it is plenty fast, has been very reliable for me, and it's only 1 process to manage, so it's simple for me to understand. If a java app server has problems, I have no idea how to easily deal with it... Is it *bad* to run it standalone? What would I gain by switching? Alan On Sep 13, 2009, at 6:19 PM, php-java-bridge- us...@li... wrote: > There is one in the CVS attic. > > However, Tomcat or JEE serv... |