Communication problem between client/server

[Michelle]

Hi all,

I have a client/server setup which I would like it to communicate
as follows:

Server:
Loop
Write something to client via writeUTF() method
(for example: loop #1 - write "A"; loop #2 - write "B")
Get input from the client via readUTF() method
(for example: loop #1 - get "X"; loop #2 - get "Y")
End loop

Client:
Loop
Read something from server via readUTF() method
(for example: loop #1 - read "A"; loop #2 - read "B")
prompt for input of something (I'm using System.in.read())
(for example: loop #1 - entered "X"; loop #2 - entered "Y")
End loop;

However, when I use System.in.read() to entered X and pressed
<CR>, the program seems sending both "X" and "<CR>" back
to the server and in loop#2, program just don't stop and prompt
for input.

Any idea?

 

[Kevin McMurtrie]

Hi all,

I have a client/server setup which I would like it to communicate
as follows:

Server:
Loop
Write something to client via writeUTF() method
(for example: loop #1 - write "A"; loop #2 - write "B")
Get input from the client via readUTF() method
(for example: loop #1 - get "X"; loop #2 - get "Y")
End loop

Client:
Loop
Read something from server via readUTF() method
(for example: loop #1 - read "A"; loop #2 - read "B")
prompt for input of something (I'm using System.in.read())
(for example: loop #1 - entered "X"; loop #2 - entered "Y")
End loop;

However, when I use System.in.read() to entered X and pressed
<CR>, the program seems sending both "X" and "<CR>" back
to the server and in loop#2, program just don't stop and prompt
for input.

Any idea?

Writing to a stream is not guaranteed to send all data through to the
other side until you call flush() or close(). Most data conversion
streams are buffered to some degree. A SocketOutputStream may or may
not be buffered, depending on the OS.

 

[Michelle]

Writing to a stream is not guaranteed to send all data through to the
other side until you call flush() or close(). Most data conversion
streams are buffered to some degree. A SocketOutputStream may or may
not be buffered, depending on the OS.

However in my case, the loop#1 seems send back both the "A" and "CR"
to the server side so that in loop#2, it does not prompt for further input.