Re: FILE* behaviour over BSD sockets - how?
From: Søren Hansen (sh_at_warma.dk)
Date: 05/13/04
- Next message: Søren Hansen: "Re: Socket Read() does not return values"
- Previous message: Alex Sisson: "Re: Detecting multiple keypresses"
- In reply to: Aurelian Melinte: "FILE* behaviour over BSD sockets - how?"
- Next in thread: Aurelian Melinte: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Aurelian Melinte: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Darko M.: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Jem Berkes: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Barry Margolin: "Re: FILE* behaviour over BSD sockets - how?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 13 May 2004 11:29:55 +0200
On Wed, 12 May 2004 18:21:19 +0000, Aurelian Melinte wrote:
> The problem: I have to use a library (which I cannot modify) with an
> API reading/writing records to FILE*. The data I have to read comes
> through a socket. The socket has been set to blocking and I successfully
> fdopen(socket). However, the API reads once in a while incomplete records
> because the underlying socket calls seem to return as soon as there is a
> packet to read but not when the whole requested number of bytes has been
> read.
I've never tried using it on sockets, but perhaps fdopen() will do the
trick?
-- Salu2, Søren.
- Next message: Søren Hansen: "Re: Socket Read() does not return values"
- Previous message: Alex Sisson: "Re: Detecting multiple keypresses"
- In reply to: Aurelian Melinte: "FILE* behaviour over BSD sockets - how?"
- Next in thread: Aurelian Melinte: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Aurelian Melinte: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Darko M.: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Jem Berkes: "Re: FILE* behaviour over BSD sockets - how?"
- Reply: Barry Margolin: "Re: FILE* behaviour over BSD sockets - how?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|