Jarvis Carroll
|
e8ef0b4304
|
buffer out-of-order messages
This took a while to debug!! Turns out I don't actually
handle datagrams that have been received before the
workers are all initialized... oops!!
|
2025-10-27 07:31:27 +00:00 |
|
Jarvis Carroll
|
b6c16967e7
|
notify router of new channels
This way the second message received on a channel should be
routed by the router without involving the fallback.
Lolspeed achieved.
|
2025-10-26 11:23:34 +00:00 |
|
Jarvis Carroll
|
47612c2775
|
have channel_man spawn its own router
Once I added dispatch_fallback to channel_man, it became clear that
the router is actually subordinate to the channel_man.
|
2025-10-26 11:14:09 +00:00 |
|
Jarvis Carroll
|
cfd9eb748f
|
rename Connection to Router
Connection is more of a supervision concept than a server concept.
I should have a SWP of SWPs too, but I can't be bothered just yet.
|
2025-10-26 10:46:27 +00:00 |
|
Jarvis Carroll
|
669b2e51e1
|
actually add msp_channel_sup.erl
oops
|
2025-10-26 10:39:08 +00:00 |
|
Jarvis Carroll
|
0ccd64e2f1
|
some kind of channel allocation
Now sending messages results in some basic channel state
tracking, but receiving doesn't do any of that yet.
|
2025-10-26 05:01:44 +00:00 |
|
Jarvis Carroll
|
7503463ff2
|
message dispatch stub
This is probably about as far as I can go without actual
manager processes... I need something that knows what
channels are in use!!
|
2025-10-26 00:25:01 +00:00 |
|
Jarvis Carroll
|
587fa1710c
|
retab
Still setting this computer up...
|
2025-10-24 12:13:57 +00:00 |
|
Jarvis Carroll
|
4d7dcf160c
|
UDP receipt
|
2025-10-24 12:06:29 +00:00 |
|
Jarvis Carroll
|
e9efcccfd0
|
initial commit
I have an implementation of reliable messages in another
repo, but I want to start over with a focus on streams.
|
2025-10-23 08:47:40 +00:00 |
|