×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 19/12/2009, at 4:02 AM, GKern@xxxxxxxxxxxxxxxx wrote:
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.
No real difference in effect. The main benefit to using a buffer is
that you can expand it once it's full if you need to stuff more data
in it (presuming you haven't yet reached the magic end-of-data marker
AND you haven't reached the maximum buffer size). Doing that with a
fixed-length variable is a bit harder.
In both cases you are reading socket data into a storage location. In
both cases you need to handle filling up that space.
With the buffer YOU are responsible for storage management. With a
fixed-length variable the system is responsible. Although you can
cheat and declare a large fixed-length variable, get a pointer to it,
and treat it like a buffer.
Note that you don't necessarily need to receive the end-of-data marker
before you can process the data. Deal with what you've received at
this point and then get the rest.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
