[Tipc-discussion] RE: tipc socket types

[Jon M. (QB/EMC) <jon...@er...>]

SOCK_RDM is for connectionless communication (using tipc_name
or tipc_portid as explicit ddesses). This communication mode
is reliable, unless you set the "unreliable" option, in which
case it becomes an equivalent to SOCK_DGRAM, i.e. unreliable
connectionless communication.

SOCK_SEQPACKET is for connection oriented, message based 
communication. Acoording to POSIX this mode should be reliable,
and it is, but a peculiarity with TIPC is that it is possible
to make it unreliable, using the "unreliable" otion. When
this option is set, messages will be discarded during congestion
or overload, instead of being returned to sender, which is the
old (and default) behaviour.

SOCK_STREAM is connection and stream oriented, just lik TCP.
It is meant to partially emulate the behaviour of TCP, but
it obeys to only a fraction of the usual TCP options, simply
because those are irrelevent to TIPC. This socket type can
not be made unreliable.

Regards /Jon

-----Original Message-----
From: Mark Haverkamp
To: Jon Maloy (QB/EMC)
Cc: tipc
Sent: 09.04.2004 12:51
Subject: tipc socket types


I have been noticing that tipc now supports a number of socket types
when creating a socket.  I have been used to the old tipc that the
socket type didn't matter.  I have found, for instance, that the only
socket type that I can do multiple sento calls on is SOCK_RDM.  Could
you discuss the different socket types supported and how they work in
tipc?

Thanks,
Mark.
-- 
Mark Haverkamp <ma...@os...>