Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

http or websocket implementation? #3

Open
sunnygleason opened this issue Jul 6, 2012 · 2 comments
Open

http or websocket implementation? #3

sunnygleason opened this issue Jul 6, 2012 · 2 comments

Comments

@sunnygleason
Copy link

Would you consider building in http/websocket support, or integrating a patch if someone contributed it? I need a ruby cube library for a project I'm working on, but UDP's lossy nature won't work for that use case...

@codykrieger
Copy link
Owner

Pull requests are welcome. :)

Sent from my iPhone

On Jul 6, 2012, at 11:20 AM, Sunny Gleason
reply@reply.github.com
wrote:

Would you consider building in http/websocket support, or integrating a patch if someone contributed it? I need a ruby cube library for a project I'm working on, but UDP's lossy nature won't work for that use case...


Reply to this email directly or view it on GitHub:
#3

@sunnygleason
Copy link
Author

Rock on - I'll see what I can whip up for review :)

On 7/6/12, Cody Krieger
reply@reply.github.com
wrote:

Pull requests are welcome. :)

Sent from my iPhone

On Jul 6, 2012, at 11:20 AM, Sunny Gleason
reply@reply.github.com
wrote:

Would you consider building in http/websocket support, or integrating a
patch if someone contributed it? I need a ruby cube library for a project
I'm working on, but UDP's lossy nature won't work for that use case...


Reply to this email directly or view it on GitHub:
#3


Reply to this email directly or view it on GitHub:
#3 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants