As I know, Akka could guaranteed message ordering for per sender-receiver pair, but not guaranteed message delivery. Erlang also similar to this. I think if to implement own sequencing, acking, and retransmission logic, this work nearly to reimplement a TCP stack. To implement a new TCP-like stack in TCP looks strange. How about just make sure only have one connection between per sender-receiver pair, so TCP could help us guaranteed message order.
- libprocess: ordered message delivery Neil Conway
- Re: libprocess: ordered message delivery haosdent
- Re: libprocess: ordered message delivery Neil Conway
- Re: libprocess: ordered message delivery Benjamin Mahler
- Re: libprocess: ordered message delivery Jojy Varghese
- Re: libprocess: ordered message delivery Neil Conway
