Hello Wesley,
> If I have LineMode off, that means I have to
> either 1) look for a terminator or 2) accept many bytes and then act
> on the information I have so far, correct?
yes
> Again, as I've seen in archive here before, what happens if my
> information gets processed in two batches (pack
OK. I understand what you're saying, which for me is a definite step
up. That being said, when would I actually act on the data that I have
received from the socket? If I have LineMode off, that means I have to
either 1) look for a terminator or 2) accept many bytes and then act
on the informa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Francois Piette wrote:
> Your ReadFully won't work. You must think event driven. When OnDataAvailable
> is triggered, you must
> read data but you can't loop waiting for so much data to come. If you have
> not received enough data,
> just get therece
Look through the demos and find a demo that uses the WSocketServer. This
component handles the connection of clients, disconnection of clients and so
on and has a list of all connected clients. And you can build your own
protocol your self. The HttpSrv component is a webserver, this is built on
to
For your server, start with SvcTcp or SrvTcp demos. The first is a service and
the later a normal
application. Both use the same "kernel".
For your client application, start from Client7 demo.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "George" <[EMAIL PROTEC
> ReadFully is another procedure I have written in hopes that I can then
> read an entire string, word, integer, what have you and read until I
> gather up enough data to continue (since I'm not using LineMode).
Your ReadFully won't work. You must think event driven. When OnDataAvailable is
trigg
