request.
This is WHY java back-ends have better
performance
and are scalable.
-Original Message-
From: tim leung [mailto:[EMAIL PROTECTED]]
Sent: Sunday, 6 May 2001 4:39 AM
To: [EMAIL PROTECTED]
Subject: JAVA vs. PERL startup time + memory
Hi,
I am
request.
This is WHY java back-ends have better
performance
and are scalable.
-Original Message-
From: tim leung [mailto:[EMAIL PROTECTED]]
Sent: Sunday, 6 May 2001 4:39 AM
To: [EMAIL PROTECTED]
Subject: JAVA vs. PERL startup time + memory
Hi,
I am
and are scalable.
-Original Message-
From: tim leung [mailto:[EMAIL PROTECTED]]
Sent: Sunday, 6 May 2001 4:39 AM
To: [EMAIL PROTECTED]
Subject: JAVA vs. PERL startup time + memory
Hi,
I am thinking of write an unix app that will get
data
from a pipe e.g
Hi,
I am thinking of write an unix app that will get data
from a pipe e.g. | and then will do a HTTP
POST to some server.
e.g. command1 | java PipeReader-- OR --
e.g. command1 | perl PipeReader
Assume I need to invoke the JVM process or PERL
process very frequently (
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, May 05, 2001 11:39 AM
Subject: JAVA vs. PERL startup time + memory
Hi,
I am thinking of write an unix app that will get data
from a pipe e.g. | and then will do a HTTP
POST to some server.
e.g. command1 | java PipeReader
your
requests out of the input), but java does threads and OO nicely.
-Original Message-
From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 05, 2001 8:44 PM
To: [EMAIL PROTECTED]
Subject: Re: JAVA vs. PERL startup time + memory
Wouldn't it be easier to create a daemon
The JVM is loaded just ONCE not once pre request.
This is WHY java back-ends have better performance and are scalable.
-Original Message-
From: tim leung [mailto:[EMAIL PROTECTED]]
Sent: Sunday, 6 May 2001 4:39 AM
To: [EMAIL PROTECTED]
Subject: JAVA vs. PERL startup time + memory
Hi
: Sunday, 6 May 2001 4:39 AM
To: [EMAIL PROTECTED]
Subject: JAVA vs. PERL startup time + memory
Hi,
I am thinking of write an unix app that will get
data
from a pipe e.g. | and then will do a HTTP
POST to some server.
e.g. command1 | java PipeReader-- OR --
e.g
Just one idea that isn't completely thought through so forgive me if this is
ludicrous
How about piping the output from the log into a FIFO/named pipe (read the
man page for mknod if you're not sure what that is). Then you could have a
background process that is reading from the pipe. That
May 2001 4:39 AM
To: [EMAIL PROTECTED]
Subject: JAVA vs. PERL startup time + memory
Hi,
I am thinking of write an unix app that will get
data
from a pipe e.g. | and then will do a HTTP
POST to some server.
e.g. command1 | java PipeReader-- OR --
e.g
10 matches
Mail list logo
