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

Juggernaut is deprecated, so it should be replaced #35

Open
s-edwards opened this issue Sep 5, 2013 · 4 comments
Open

Juggernaut is deprecated, so it should be replaced #35

s-edwards opened this issue Sep 5, 2013 · 4 comments

Comments

@s-edwards
Copy link
Member

Juggernaut has been deprecated by its author (over a year ago) and is no longer being developed. It needs to be replaced at some point.

See: http://blog.alexmaccaw.com/killing-a-library

@ArturAguiar
Copy link
Member

I'm having a bad time trying to install and properly setup juggernaut on my local machine. It has been deprecated for more than 2 years now. Following from the README in the official repo, the Node Packaged Modules (npm) is failing to fetch from the juggernaut registry, so I'm not sure how to install it anymore. Installing the juggernaut gem is not enough.

It might be time to switch to another solution. If so, would the HTML5 Server-Sent Events mentioned by Maccaw be the best choice?

@ashimaathri
Copy link
Contributor

I will work on that right after I finish writing tests for the models.

@allevato
Copy link
Member

I spent a little bit of time (very little) trying to get HTML5 SSE working to replace Juggernaut. This looks like what I used as a guide:

http://tenderlovemaking.com/2012/07/30/is-it-live.html

(I hate that domain name, it makes it look like I'm spamming.)

Something that I was never able to solve was that once I had the streaming connection up between the client and server, it blocked the server from handling any more requests (like opening a new tab connecting to a different page on the site). I never had the time to figure out whether the deadlock was within Rails or on the webserver itself being unable to process the request until the previous connection was closed, and I had to abandon it.

Just something to be aware of while you embark down this road. I think SSE is the way to go if that problem can be solved — I'm not aware of any better solutions.

One other caveat: SSE still isn't supported in IE. At the time I started Pythy, I didn't care about supporting IE, but I don't know if you do now.

@ashimaathri
Copy link
Contributor

@allevato, thanks for the information. I'll keep that in mind.

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

4 participants