asynchronous - Same Machine Erlang communication -


To help me understand what approach I should take for interface with Erlang, I need to answer the following question: I <...

The AFAIK Eerling uses a multi-process approach on a SMP Unix box in this case it should do the same machine IPC.

  1. Does Eranang use the Unix domain socket for UNIX?
  2. Does it use name-pipe for windows?

  3. If it does not apply the above two structures - that is, not designated pipes for windows; It has to fallback on sockets on windows.

  4. How are the principles given above implemented, whether they use message oriented, thread per single channel, asynchronous structure or something else?

  5. If my line of argument is wrong, does it use a master-hair tree and all other processes indirectly - through the master?

- 1 -

for Erring Binary Format Documentation.

The Universal Consent That Unix Domain Sockets Performs Better I think that I will try to expand Erlang to use the better preferences provided. I also strongly suspect that APOL and windows IOPC are not used in TCP / IP event loop - I will post back after auditing the code.

One more says that altong, in reality, does not support anything other than TCP and UDP.

There are two erasing libraries for communication and

Ergon allows unix dome socket to be opened under UNIX.

R1 This TCP / IP (In fact, any "standard" support for Unix domain sockets Is not)

R2 I am pretty sure that it is still TCP / IP sockets

see R3 R2

for R4 Erlang A binary currency format is appropriate and this message is based on. Exchange can either be synced (like RPC-like) or async.

R5 No Master.


As a bonus (to help you save time): Inter-node communication (using a registered name (-ai name or-name) to use either RPC Do not forget or whatever).


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

jquery - SimpleModal Confirm fails to submit form -