«

I don't know if Unix sockets (or named sockets) are C standard. I
think so, so I post on this ng.

I need to have a bidirectional communication between two different
process on the same computer. I'm using named socket with success.

The protocol is on a text basis and is based on messages with an
ending newline character (\n).

Is it possible to have a stream pointer (FILE *) from the socket file
descriptor so I'll be able to use fprintf() and similar functions?

pozz <> writes:
> I don't know if Unix sockets (or named sockets) are C standard. I
> think so, so I post on this ng.

They aren't. Try comp.unix.programmer.

[...]

--
Keith Thompson (The_Other_Keith) kst- <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

On 03/25/2011 02:53 PM, pozz wrote:
> I don't know if Unix sockets (or named sockets) are C standard. I
> think so, so I post on this ng.

No they're not.

<Off-topic>
If you want to work with them, I'd strongly recommend getting your
hands on a copy of <http://www.kohala.com/start/unpv12e.html>
</Off-topic>

Mark Bluemel wrote:
> On 03/25/2011 02:53 PM, pozz wrote:
>> I don't know if Unix sockets (or named sockets) are C standard. I
>> think so, so I post on this ng.
>
> No they're not.
>
> <Off-topic>
> If you want to work with them, I'd strongly recommend getting your
> hands on a copy of <http://www.kohala.com/start/unpv12e.html>
> </Off-topic>

Great book. I've got it.

Bill