[libinline-java-perl] 208/398: To save some blabla that's there

[Jonas Smedegaard]

This is an automated email from the git hooks/post-receive script.

js pushed a commit to tag 0.55
in repository libinline-java-perl.

commit 312d77e064b3caf4a12aa5992b93d633abd50d11
Author: patrick_leb <>
Date:   Fri Jan 17 03:17:21 2003 +0000

    To save some blabla that's there
---
 TODO | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/TODO b/TODO
index 6b90795..c504bf9 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,40 @@
 CODE:
 - Check INFO flag vs. PRINT_INFO (shortcuts not working?)
 - Fix for Java 1.4 (reflection inverting method/member order)
+- Improve documentation of issues:
+- Include patch by Doug MacEachern
+
+
+These tips should get you going:
+
+ - Take note that in SHARED_JVM mode, System.out is closed(). This is
+ necessary
+   in order for the process to detach itself properly on certain platforms.
+ Anyway only the
+   processs that actually started the JVM could see the output. Maybe a log
+ file would be a good
+   idea... I'll think about that.
+
+ - Try running it without SHARED_JVM first. It's a lot easier to debug. First
+ you get System.out, second
+   JVM restarts each time, so when you change your Java code you don't need
+ to kill the JVM manually.
+   Anyways I don't think in your case your need SHARED_JVM. SHARED_JVM is
+ really meant to be used
+   when your Perl script is a CGI/mod_perl module where you get many requests
+ and you can't afford
+   the JVM startup delay every time. It's also useful if you need to share
+ data betwen each of your script
+   invocations (if your use 'static' data in your Java class, all the script
+ invocations can access the data and it's
+   persistent between accesses).
+
+
+ I'm taking note of these details and I'll beef up the documentation of these
+ issues.
+
+
+
 
 TEST:
 - Alpha

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libinline-java-perl.git