Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate ActionCable integration #196

Open
ajb opened this issue Jul 11, 2015 · 1 comment
Open

Investigate ActionCable integration #196

ajb opened this issue Jul 11, 2015 · 1 comment
Milestone

Comments

@ajb
Copy link
Collaborator

ajb commented Jul 11, 2015

No description provided.

@ajb ajb added the enhancement label Feb 6, 2016
@aeberlin
Copy link

I think that #212 will actually make this easier to wrap minds around. If we refine the STOMP/websocket configuration vars and generalize those in Pusher, the bulk of the work would be building out ActionCable::Connection::Base interfaces and integrating it with the partial architecture.

The ActionCable effort looks very similar to the Stilts platform used by TorqueBox. Eerily similar.

It appears similar to STOMP, but I don't have the time atm to dig in more and see if it matches spec.

Do you know, @ajb?

@ajb ajb modified the milestone: 2.0 Feb 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants