tcp/ip and Erlang

Sean Hinde <>
Thu May 17 13:33:16 CEST 2001


There is a file in:

erts/emulator/internal_doc/erl_ext_dist.txt which has some explanation. I've
no idea if this is up to date or not.

If you want to check how something is defined in the external term format
you can use:

1> term_to_binary(1).
<<131,97,1>>
2> term_to_binary([1,2,3]).
<<131,107,0,3,1,2,3>>
3> binary_to_term(<<131,107,0,3,1,2,3>>).
[1,2,3]

- Sean

> -----Original Message-----
> From: Karel Van Oudheusden [mailto:]
> Sent: 17 May 2001 12:08
> To: 
> Subject: tcp/ip and Erlang
> 
> 
> First of all I would like to thank every one for the answers 
> I received
> for my previous question.  They were very helpful.
> 
> 
> I just have a short second question.  I am planning to work 
> distributed
> over different Erlang nodes with TCP/IP.  I am also planning to use
> Ethereal (or tcpdump) to observe the packets that are sent between two
> Erlang nodes. To correctly interpret the data bits of the packets, I
> have to understand how Erlang puts the Erlang data in this 
> TCP format. 
> In addition I am interested in how the sender PID (of the sending
> process) and the receiver PID (of the receiving process on another
> computer) are stored in the data part of the packet.
> 
> 
> Any hints are welcome.  I'd probably be able to find this out 
> by myself,
> but I am short in time.  Therefore any help would be great. If anybody
> has written code to interpret Erlang packets (in conformance with
> TCP/IP) and doesn't mind sharing it, please inform me.
> 
> 
> 
> thanks a lot,
> Karel.
> 



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.





More information about the erlang-questions mailing list