Sun Jul 15 13:05:46 CEST 2007
prim_inet is not documented because it is not intended to be a
supported/stable API which we will keep backwards compatible.
prim_inet is only supposed to be used by modules such as gen_udp,
gen_tcp, gen_sctp, inet etc. which are supported and documented API's.
If important functionality is missing in the supported API's it should
be added there and probably in a slightly different way than in
prim_inet (but built on prim_inet).
The general principle that we follow is that what's not documented is
not supported and tested and might change, dissapear or whatever
/Kenneth (Erlang/OTP team at Ericsson)
On 7/15/07, Ben Hood <0x6e6562@REDACTED> wrote:
> I've come accross the prim_inet module in some code and I'm trying to
> understand what it does as it doesn't seem to have a man page.
> Going by a few posts I've googled, it seems to handle socket
> connections in a non-blocking fashion and also seems to abstract UDP,
> TCP and SCTP to a common receiving/sending interface.
> Does anybody know of any documentation, examples or even a general
> explanation for prim_inet?
> erlang-questions mailing list
More information about the erlang-questions