-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Poll] Real-time stuff or caching? #52
Comments
im going to say #51 |
I'm going with #51 too. |
#51 no doubt. |
Definitely #51 (now that this has been brought to my own attention). WebSocket support in particular is becoming increasingly handy, and it's already supported by Cowboy and (I'm pretty sure) Plug; we just need to leverage those features (perhaps by referring to their implementations in, say, Pheonix or Weber and making them more... Sugary). |
@YellowApple. definitely agree about referencing Phoenix and Weber when implementing it for Sugar. An older version of Phoenix is what I had in mind when I originally made the high level plan above. Websockets are definitely supported by Cowboy ( I've used it in production before ), but from what I've seen, plug doesn't have support quite yet since they want to ensure consistency across all possible adapters. I believe they are using Phoenix as a test bed for a future integration in Plug. if anyone has info on that that differs, please let me know |
For those that expressed interest in WebSocket support, care to give thoughts? #51 (comment) |
Which should go first, #17 or #51? Any preferences?
At this point, I'm leaning towards real-time stuff because it's a little more straight-forward with less in the air regarding implementation, but I could be swayed either way.
The text was updated successfully, but these errors were encountered: