You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Is it possible or not-too-stupid to package only the Ratchet\RFC6455\Messaging namespace?
I am making a small HTTP/1.1 server crammed with only necessary features and I'd like to add websockets.
However, I don't want guzzle and I'll implement handshake myself.
I can just copy the namespace, but if (unlikely) my little project evolves to publish-worthy, I don't want to pull guzzle and psr interfaces.
Otherwise, my options would be to copy the Messaging folder and reference where I got it from (if license does not change in future).
Or implement RFC6455 from scratch, which I don't want to do.
The text was updated successfully, but these errors were encountered:
Hello,
Is it possible or not-too-stupid to package only the Ratchet\RFC6455\Messaging namespace?
I am making a small HTTP/1.1 server crammed with only necessary features and I'd like to add websockets.
However, I don't want guzzle and I'll implement handshake myself.
I can just copy the namespace, but if (unlikely) my little project evolves to publish-worthy, I don't want to pull guzzle and psr interfaces.
Otherwise, my options would be to copy the Messaging folder and reference where I got it from (if license does not change in future).
Or implement RFC6455 from scratch, which I don't want to do.
The text was updated successfully, but these errors were encountered: