[Mono-list] Questions on Mono.Unix.Pipes

[mickeyf]

>> the mono documentation that I have found is missing or incomplete. 

..Or maybe it's just a Monday morning and I haven't had any coffee yet.

Thank you - very helpful. It's never clear to me how much of the MSDN
documentation I can rely on to apply to Mono. Windows .NET doesn't actually
have anything 'called' UnixStream, so I was hesitant to assume that a stream
is stream and that all methods etc can always be directly applied. 

>> and does this guarantee that both the write and the read are atomic and
>> that all bytes will in fact be read in a single read on the read end of
>> the pipe?

>As far as I am aware, _nothing_ can guarantee that. I could be wrong. 

Although I have been using this pipe with apparent success, I am looking at
sockets as an alternative, and found this as a possibility for AF_LOCAL:

/
SOCK_SEQPACKET

    Provides a sequenced, reliable, two-way connection-based data
transmission path for datagrams of fixed maximum length; a consumer is
required to read an entire packet with each input system call./

I'm new to socket programming so whether this works quite as I understand
and hope it to, I guess I'll find out. 

Ultimately what I am dealing with is the message boundary problem, and
messages potentially getting out of sync even though I know the length. I'd
like to manage this in the cleanest way available. If I stick with pipes I
may try wrapping the message with begin and end tokens and looking for those
on the consuming end.





--
View this message in context: http://mono.1490590.n4.nabble.com/Questions-on-Mono-Unix-Pipes-tp4657794p4657810.html
Sent from the Mono - General mailing list archive at Nabble.com.