Steve Horsley schreef:
> [EMAIL PROTECTED] wrote:
> > Steve Horsley schreef:
> >
> >
> >>Probably the same problem. If you didn't send a 2 byte length
> >>indicator first, then java's readUTF() will have tried to
> >>interpret the first 2 bytes that you did actually send as the
> >>string length,
[EMAIL PROTECTED] wrote:
> Steve Horsley schreef:
>
>
>>Probably the same problem. If you didn't send a 2 byte length
>>indicator first, then java's readUTF() will have tried to
>>interpret the first 2 bytes that you did actually send as the
>>string length, and may well simply be waiting patient
Steve Horsley schreef:
> [EMAIL PROTECTED] wrote:
> > Dear newsgroup,
> >
> > I give up, I must be overseeing something terribly trivial, but I can't
> > get a simple (Java) applet to react to incoming (python) SocketServer
> > messages.
> >
> > Without boring you with the details of my code (on
[EMAIL PROTECTED] wrote:
> Dear newsgroup,
>
> I give up, I must be overseeing something terribly trivial, but I can't
> get a simple (Java) applet to react to incoming (python) SocketServer
> messages.
>
> Without boring you with the details of my code (on request available,
> though), here is w
Dear newsgroup,
I give up, I must be overseeing something terribly trivial, but I can't
get a simple (Java) applet to react to incoming (python) SocketServer
messages.
Without boring you with the details of my code (on request available,
though), here is what I do :
I have a TCPServer and BaseRe
