Re: Receiving large text strings with RECV api question

Thanks Simon, Vern, and Scott for your input.

"You need to receive data from the socket until:
a) Some end-of-data indicator is received"

In Scott's example this is done in a loop (DOU char = x'0a') - except that
I encountered a never ending loop since the end of data character is
beyond the boundary of the field size (as defined in the data parameter
shown below).

"Don't think of it as a fixed-length piece of data. Therein lies madness.
Think of it as a continuous stream of data..."

I guess this is where I'm getting confused Scott. I understand what you
said regarding the data stream (and the roller coaster is a good analogy),
but I guess my 'fixed length' thinking comes from looking at the prototype
for TRECVLINE and the data parameter being defined as 32702.

D trecvline PR 10I 0
D sock 10I 0 value
D data 32702A varying options(*varsize)
D size 10I 0 value
D timeout 10I 0 value

Now I just looked at the socket tutorial and see that the recv api in the
tutorial uses a pointer to the buffer instead of a defined variable.
Perhaps this is where my problem (and confusion) is.

"A socket program ought to be able to handle however much data is sent to
it. [...] You'll still have to receive the rest of what is sent else it
will remain for
the next receive operation."

And that's how I understand it, thanks for clarifying Simon.

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.