Implement server #2
Conversation
| method listen() { | ||
| supply { | ||
| whenever self.socket-provider.listen($!host, $!port) -> $conn { | ||
| my $connection = Connection.new(:$conn); |
There was a problem hiding this comment.
I'm wondering whether the Connection should have a Promise that is kept when the CONNECT has been completed (which lets us do the authentication or whatever as well,) so that it's not emitted before we have a valid connection.
There was a problem hiding this comment.
I've implemented that simply. I think there needs to be a hook for authentification.
jonathanstowe
force-pushed
the
implement-server
branch
from
1433106 to
0603ea5
Compare
| body => .message; | ||
| } | ||
| }; | ||
| $!connected.keep: True; |
There was a problem hiding this comment.
I think there also needs to be a timeout (set as a property of the server,) whereby the connection is closed if the 'CONNECT' or 'STOMP' isn't received.
|
Can't believe this was four years ago. How time flies. Anyhow I've got an idea that may off two birds which imma try make a PoC over the weekend. |
jonathanstowe
force-pushed
the
implement-server
branch
from
a07c699 to
52c5152
Compare
|
I've rebased with a view to merging at some point, but in the intervening years I've come to the view that it would make more sense to re-implement in terms of |
Specifically this provides an implementation of the SUBSCRIBE/UNSUBSCRIBE commands and a Connection object. This is sufficient to make a Stomp server.
jonathanstowe
force-pushed
the
implement-server
branch
from
52c5152 to
dceb8ea
Compare
|
I'd like to merge this but there appears to be a problem with the tests on Windows if someone has the wherewithal to diagnose that. |
|
The Windows is fixed. The MacOS failure on the last run could conceivably happen on any platform, the pattern used in the test may be unreliable depending on the number of threads available, system load etc. |
Very simplest implementation of a server with fan-out pattern