Yep I aggree. Layering streams over sockets
is very useful for most apps. However there
can be issues with buffering etc. and you
still have no control over the lower level
TCP buffers that I think John Carter was
referring to. Just to confirm, if you are
using streams over sockets, then to flush
the stream buffer use fflush. You can control
the buffering of streams so that the buffers
are flush automaticaly on newlines for e.g.
See setbuf() and co.
> -----Original Message-----
> From: Caolan McNamara [mailto:cmc at stardivision.de]
> Sent: 25 April 2000 19:03
> To: ILUG
> Subject: RE: [ILUG] force socket to write
>>> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>> On 25.04.00, 18:53:09, "Brady, Padraig"
> <Padraig.Brady at compaq.com> wrote
> regarding RE: [ILUG] force socket to write:
>>> > I think this only applies to streams,
> > and hence will not work for sockets?
> > Messing with protocol buffers is not
> > trivial.
>> Personally whenever I can, I fdopen the file descriptor returned by
> socket and use that FILE *. Much more robust and safe, no
> fixed length
> arrays to worry about overwriting. Its fine for uncomplicated things.
> Irish Linux Users' Group: ilug at linux.ie>http://www.linux.ie/mailman/listinfo/ilug for
> (un)subscription information.
> List maintainer: listmaster at linux.ie>
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!