… | |
… | |
727 | |
727 | |
728 | If an optional time-out (in seconds) is given and it is not C<undef>, |
728 | If an optional time-out (in seconds) is given and it is not C<undef>, |
729 | then the callback will be called without any arguments after the time-out |
729 | then the callback will be called without any arguments after the time-out |
730 | elapsed and the port is C<kil>ed. |
730 | elapsed and the port is C<kil>ed. |
731 | |
731 | |
732 | If no time-out is given, then the local port will monitor the remote port |
732 | If no time-out is given (or it is C<undef>), then the local port will |
733 | instead, so it eventually gets cleaned-up. |
733 | monitor the remote port instead, so it eventually gets cleaned-up. |
734 | |
734 | |
735 | Currently this function returns the temporary port, but this "feature" |
735 | Currently this function returns the temporary port, but this "feature" |
736 | might go in future versions unless you can make a convincing case that |
736 | might go in future versions unless you can make a convincing case that |
737 | this is indeed useful for something. |
737 | this is indeed useful for something. |
738 | |
738 | |
… | |
… | |
787 | |
787 | |
788 | =item * Node IDs are arbitrary strings in AEMP. |
788 | =item * Node IDs are arbitrary strings in AEMP. |
789 | |
789 | |
790 | Erlang relies on special naming and DNS to work everywhere in the same |
790 | Erlang relies on special naming and DNS to work everywhere in the same |
791 | way. AEMP relies on each node somehow knowing its own address(es) (e.g. by |
791 | way. AEMP relies on each node somehow knowing its own address(es) (e.g. by |
792 | configuration or DNS), but will otherwise discover other odes itself. |
792 | configuration or DNS), and possibly the addresses of some seed nodes, but |
|
|
793 | will otherwise discover other nodes (and their IDs) itself. |
793 | |
794 | |
794 | =item * Erlang has a "remote ports are like local ports" philosophy, AEMP |
795 | =item * Erlang has a "remote ports are like local ports" philosophy, AEMP |
795 | uses "local ports are like remote ports". |
796 | uses "local ports are like remote ports". |
796 | |
797 | |
797 | The failure modes for local ports are quite different (runtime errors |
798 | The failure modes for local ports are quite different (runtime errors |
… | |
… | |
822 | so does not need a queue that can overflow). AEMP sends are immediate, |
823 | so does not need a queue that can overflow). AEMP sends are immediate, |
823 | connection establishment is handled in the background. |
824 | connection establishment is handled in the background. |
824 | |
825 | |
825 | =item * Erlang suffers from silent message loss, AEMP does not. |
826 | =item * Erlang suffers from silent message loss, AEMP does not. |
826 | |
827 | |
827 | Erlang makes few guarantees on messages delivery - messages can get lost |
828 | Erlang implements few guarantees on messages delivery - messages can get |
828 | without any of the processes realising it (i.e. you send messages a, b, |
829 | lost without any of the processes realising it (i.e. you send messages a, |
829 | and c, and the other side only receives messages a and c). |
830 | b, and c, and the other side only receives messages a and c). |
830 | |
831 | |
831 | AEMP guarantees correct ordering, and the guarantee that after one message |
832 | AEMP guarantees correct ordering, and the guarantee that after one message |
832 | is lost, all following ones sent to the same port are lost as well, until |
833 | is lost, all following ones sent to the same port are lost as well, until |
833 | monitoring raises an error, so there are no silent "holes" in the message |
834 | monitoring raises an error, so there are no silent "holes" in the message |
834 | sequence. |
835 | sequence. |