Message lost on 2 separate connections to same URL about pawl

[SimonFrings]

Hey @bobrundle, thanks for bringing this up 👍

I've fixed this by queuing up the messages to the same URL and sending them together on the same connection. A much better design, I admit.

Sounds good, this is definitely the better design to use here.

Why do back-to-back messages on separate connections to the same URL fail?

Hard to say to be honest. Is there no output (client or server side) at all for the "discarded" message? This might also depend on how much time each connection needs, maybe the second one is faster or is it possible to achieve different results (only one of them being "discarded" , depending on which connection comes first)? Any additional input is welcome in order to get some more information on this.

FYI: The Ratchet namespace for \ratchet\client\connect(…) should always be camelcase: \Ratchet\Client\connect(…)