Reading from an Socket and it hands at in.readline()!=null

[saumil baxi]

Hi,

I am writing a simple server client application,
at the server end whenever a client connects , server reads data and response back
but the server gets hang at bufferin.readline()

Socket connection = service.accept();
 	
BufferedInputStream bufferedInputStream = new BufferedInputStream(connection
						.getInputStream()); 
InputStreamReader in = new InputStreamReader(bufferedInputStream);
				
BufferedReader bufferin = new BufferedReader(in);
String request ="";
String read = "";
while((read=bufferin.readLine())!=null){	
	request += read;
	System.out.println(read);
}

What is the best way to avoid if the client doesn't send an EOM. how to tell the server to stop reading from the Stream.

[Ulf Dittmer]

Start here: Don't println to a Socket. readline() has the same problem.

[Tom Reilly]

Start here: Don't println to a Socket.

That link displayed (redirected to?) http://developer.apple.com/library/mac/navigation/index.html#topic=Technical+Notes§ion=Resource+Types. Was that your intention?

[Ulf Dittmer]

Tom Reilly wrote:That link displayed (redirected to?) http://developer.apple.com/library/mac/navigation/index.html#topic=Technical+Notes§ion=Resource+Types. Was that your intention?

Ugh, no it wasn't. Thanks for pointing that out. I can't believe they removed that article - at least it looks like they did, I can't find it on their site now. The Japanese version is still there :-)

The bottom line is: one can't reliably use "println" and "readLine" with sockets due to those methods using the default line ending that is appropriate for the platform the code runs on. Most protocols (HTTP, for example) use "\r\n" for line endings, though.

Update: I've put up an archived version of the article here.

[saumil baxi]

Thanks a lot Ulf Dittmer.