Open tonyg opened 10 years ago
I think we should do the opposite and make this provide the same interface as net/websocket optionally. It is good to split up code into many pkgs imho.
If we do that, I think it would be helpful to rename this package websocket
and move this code into the net/websocket
collection, since rfc6455
isn't a very descriptive name.
Any further thoughts on this, a year later? I’d still appreciate renaming this package to websocket
and exposing net/websocket
, then just having rfc6455
reprovide everything.
Go for it!
On Thu, Jan 14, 2016 at 3:25 AM, Alexis King notifications@github.com wrote:
Any further thoughts on this, a year later? I’d still appreciate renaming this package to websocket and exposing net/websocket, then just having rfc6455 reprovide everything.
— Reply to this email directly or view it on GitHub https://github.com/tonyg/racket-rfc6455/issues/2#issuecomment-171570223.
Jay McCarthy Associate Professor PLT @ CS @ UMass Lowell http://jeapostrophe.github.io
"Wherefore, be not weary in well-doing,
for ye are laying the foundation of a great work.
And out of small things proceedeth that which is great."
The intention here is to replace the existing Racket websocket code with this code, and mark this package as for legacy use only. /cc @samth