Re: Sockets, writing data and shutdownOutput
- From: "HK" <pifpafpuf@xxxxxx>
- Date: 2 Aug 2005 07:19:51 -0700
jan V wrote:
> > I use the shutdownOutput to make sure the server
> > understands that we are done and no more data can
> > be expected, but it seems that it overinterpretes
> > it as if my client is not interested in
> > pending response data?
>
> Why don't you socket.shutdownOutput() in your main thread, after you;ve
> fully received the web server's response? Why do you have to call it so
> early, before having processed the reply?
I want to make sure that even the last byte
of data gets through to the server and is
not lingering somewhere in an output
buffer of the client. If the data is not
completely send, the response cannot be
complete and then the client will never
get the chance to call shutdownOutput()
if it waits until after it has received
all the response data.
Harald.
.
- Follow-Ups:
- Re: Sockets, writing data and shutdownOutput
- From: jan V
- Re: Sockets, writing data and shutdownOutput
- References:
- Sockets, writing data and shutdownOutput
- From: HK
- Re: Sockets, writing data and shutdownOutput
- From: jan V
- Sockets, writing data and shutdownOutput
- Prev by Date: Re: JProgressBar not displaying or updating (also on java.gui - sorry)
- Next by Date: Re: J2EE protection
- Previous by thread: Re: Sockets, writing data and shutdownOutput
- Next by thread: Re: Sockets, writing data and shutdownOutput
- Index(es):
Relevant Pages
|