Yes, that is correct.
The process for each 3 is real small, but their could be up to a million
lines, potentially.
I was hoping to be able to build everything into a Tomcat servlet, and
be done with it. ;-) I'll do some more testing and see what I can find.
Thanks for everyones help.
Andre P
I see, you're thinking in Sockets
Sockets are usually :
1. open connection
2. give start byte
3. keep streaming the job byte
4. give the stop byte
The question is. How long is the number 3 ? how long between the 1st adduser
and the 2nd adduser ? if its very short then you can use put, if not...
On 12/19/06, Scott Carr <[EMAIL PROTECTED]> wrote:
adduser can be an unlimited amount of times. I want to process the
lines as they come into the Servlet, that way a seperate process could
be doing something to complete each of the tasks, while I am in the
process of working on reading the line
Why dont you try using PUT instead of POST ? I think put is more suitable
for this as you can stream anything to servlet.
if you insist on using post, i recommend getting the parameter and replace
the newline with some chars like ':'
this is an example on streaming an object using put
Htt
I am creating a client - server application that will process lines like:
startjob
adduser
adduser
adduser
adduser
endjob
adduser can be an unlimited amount of times. I want to process the
lines as they come into the Servlet, that way a seperate process could
be doing something to complete ea
Why do you want to read POST by using reader ? I only use the stream from
request on a PUT request.
On 12/16/06, Scott Carr <[EMAIL PROTECTED]> wrote:
Hassan Schroeder wrote:
> On 12/15/06, Scott Carr <[EMAIL PROTECTED]> wrote:
>> Does a servlet require the use of a Content-Length for the Read
Understand. The chunk stuff is what I am planning on using. Do you
know if Tomcat waits until all chunks are in before starting the Servlet
processing?
Bill Barker wrote:
If you don't send a Content-Length, then you need to use 'Transfer-Encoding:
chunked'. Otherwise Tomcat (or any other HT
If you don't send a Content-Length, then you need to use 'Transfer-Encoding:
chunked'. Otherwise Tomcat (or any other HTTP/1.1 server) has no way of
knowing when the request body ends, and the next request begins.
"Scott Carr" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Does
On 12/15/06, Scott Carr <[EMAIL PROTECTED]> wrote:
Hm, the reason I asked, is because of a test I ran. strLine is always null.
Here's the simple test method I used:
protected void doPost(HttpServletRequest request,
HttpServletResponse response)
throw
Hassan Schroeder wrote:
> On 12/15/06, Scott Carr <[EMAIL PROTECTED]> wrote:
>> Does a servlet require the use of a Content-Length for the Reader to be
>> populated?
>
> A pretty cursory test seems to indicate not, but I could just be lucky
> :-)
>
>> ...and I want to read each line as they come in
On 12/15/06, Scott Carr <[EMAIL PROTECTED]> wrote:
Does a servlet require the use of a Content-Length for the Reader to be
populated?
A pretty cursory test seems to indicate not, but I could just be lucky :-)
...and I want to read each line as they come in, and handle the request on
a line by
Assuming a client would be requesting data via your servlet, I don't believe
there is a limit. Your sevlet calls PrintWriter.write(..) and that
implements buffering that would flush onces the buffer is full.
On 12/15/06, Scott Carr <[EMAIL PROTECTED]> wrote:
Does a servlet require the use of a
Does a servlet require the use of a Content-Length for the Reader to be
populated?
I trying to use Tomcat instead of writing my own Socket Server. I have
a set of lines that I am trying to parse, but I don't have any idea how
much is going to be sent up front.
It may be 1000Kb, or it may be
13 matches
Mail list logo
