[Info-vax] Assembly languages

[Arne Vajhøj]

On 4/13/2022 10:08 AM, Johnny Billquist wrote:
> On 2022-04-12 14:33, Simon Clubley wrote:
>> On 2022-04-12, gah4 <gah4 at u.washington.edu> wrote:
>>> On Monday, April 11, 2022 at 11:42:00 PM UTC-7, Johnny Billquist wrote:
>>>
>>>> For networking, it's all carried by IP datagrams in the end, which are
>>>> blocks. TCP then implements a stream of bytes abstraction on top of 
>>>> that.
>>>
>>> Yes, but TCP won't tell you were the boundaries were before the data
>>> went into the TCP stream, or where the IP boundaries were.
>>
>> I wonder if there are any programmers still around that try to
>> treat TCP as if it was record based anyway. :-)
>>
>> I know that in the old days, you sometimes came across reports of
>> people that assumed one TCP write in a program turned into exactly
>> one read in the receiving program...
> 
> Lots of people still believe that. I had to clarify this to a colleague 
> only the other day.

Happens all the time.

Some technologies makes it easier to avoid. Both Java
and .NET has a stack:

Java BufferedReader & Print Stream / .NET StreamReader & StreamWriter - 
handle read & write of lines of text
Java InputStream & OutputStream / .NET Stream - handle read & write of 
byte stream
Java Socket / .NET TcpClient - handle open not read & write

The highest level hides the read loop to read all needed.

Arne