Both ends of the socket communications are straight Java code. It is very
simple.
On the GWT side, both halves, client and server, communicate via standard
GWT communications mechanisms. The GWT server end and the foreign Java
server it is communicating with occurs in Java over socket communicat
How the client deal with socket?
On Apr 17, 3:46 am, Blake McBride wrote:
> I thought I would give a little more information and a short example. The
> server side handles multiple connections via threads. Communications code
> on both side look the same. Here is a sample:
>
> s = new Socket((
I thought I would give a little more information and a short example. The
server side handles multiple connections via threads. Communications code
on both side look the same. Here is a sample:
s = new Socket((String) null, 2000);
OutputStream out = s.getOutputStream();
InputStream in = s.ge
Greetings,
Attempting to communicate bidirectionally between a GWT app and another
Java server (on the same machine or not) proved to be a bit of a challenge
for me (i.e. getting past the SOP restriction, bidirectional
communications, and structured communications). After a lot of head
banging, s
