Might work on a LAN, but it may fail on anything slower.
-Original Message-
From: Peter Harrison IT [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, July 14, 1999 12:20 PM
To: Multiple recipients of list delphi
Subject:RE: [DUG]: TCP/IP Question
File: ATT4.txt; charset
'record' there
should be no problems.
-Original Message-
From: Nic Wise [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, July 13, 1999 3:02 PM
To: Multiple recipients of list delphi
Subject:Re: [DUG]: TCP/IP Question
Define packets. If you mean:
send block A (which might be 16K
To: Multiple recipients of list delphi
Subject: RE: [DUG]: TCP/IP Question
TCP has the concept of a session. So block B will definitely be delivered
down a socket after block A.
The only think likely to confuse the receiving program is the fact that
the receiving socket may get it in peculiar
: Wednesday, July 14, 1999 9:53 AM
To: Multiple recipients of list delphi
Subject: RE: [DUG]: TCP/IP Question
Hokay, - how can I tell when I have received a full record-
ie all packets
have been received from the clients send (multiple packets make a full
record.)?
-Original Message
Think of it as like reading a binary disk file. As long as you know enough
about the structure you should be able to decode it into records as you
read it. This is complicated by not having everything available immediately
at the start, but with a bit of thought you can work around this. A simple
Subject: RE: [DUG]: TCP/IP Question
Hokay, - how can I tell when I have received a full record- ie all
packets
have been received from the clients send (multiple packets make a full
record.)?
---
New Zealand
ÿþ<
Interesting page of HTML Codes... I wonder what it actually says. Not all of
us have got clever email readers. Plain text would be good. :)
Not to mention the increased bandwidth for content ratio. This has been bashed
about before and I think the result was something like:
1. No binaries
2.
Thanks everyone for your replies. I now have my server working just great.
The solution was to move a set length of data to my output stream from the
input socket each time the OnDataAvailable event fired.
The result of this is that the OnDataAvailable event keeps firing until the
socket is
Re RTF email - oops :-}
---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
AFAIK, TCP/IP should enforce the sequence in which data is received by your
listener.
It certainly seems to do this ok on my TCP/IP listener. However, it depends
what you mean by "packets".
In my app, I send anything up to 1mb files from a sender on one machine
(PC) to a receiver on another
Define packets. If you mean:
send block A (which might be 16K, for all I know)
send block B
they _could_ come in as B then A
BUT, TCP/IP will make sure that all of A - if its 16K, it gets split up
into MTU-sized blocks (512 or 1024bytes or whatever its set to) - is in
the right order.
N
Yes - this is my problem. I need to think about this some more...
-Original Message-
From: Nic Wise [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 13, 1999 03:02 PM
To: Multiple recipients of list delphi
Subject: Re: [DUG]: TCP/IP Question
Define packets. If you mean:
send block
ÿþ< ! D O C T Y P E H T M L P U B L I C " - / / W 3 C / / D T D H T M L 4 . 0 T r a n s i t i o n a l / / E N " >
< H T M L > < H E A D >
< M E T A c o n t e n t = " t e x t / h t m l ; c h a r s e t = u n i c o d e " h t t p - e q u i v = C o n t e n t - T y p e >
14 matches
Mail list logo
