sugar-framework / sugar

Modular web framework for Elixir

https://sugar-framework.github.io/

MIT License

430 stars 29 forks source link

[Poll] Real-time stuff or caching? #52

Open slogsdon opened 9 years ago

slogsdon commented 9 years ago

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.

CrowdHailer commented 9 years ago

im going to say #51

vjustov commented 9 years ago

I'm going with #51 too.

rubencaro commented 9 years ago

51 no doubt.

YellowApple commented 9 years ago

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).

slogsdon commented 9 years ago

@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

slogsdon commented 9 years ago

For those that expressed interest in WebSocket support, care to give thoughts? https://github.com/sugar-framework/sugar/issues/51#issuecomment-96428453