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

Find an alternative to websocket implementation #116

Open
5 tasks
nemesifier opened this issue Feb 23, 2014 · 0 comments
Open
5 tasks

Find an alternative to websocket implementation #116

nemesifier opened this issue Feb 23, 2014 · 0 comments
Labels
Milestone

Comments

@nemesifier
Copy link
Member

We should replace the initial prototype websocket implementation with a more mature solution.

I've been following a few projects:

We need a solution that allows us to do mainly 3 things:

  • send notifications
  • update the UI when data changes
  • streamline loading huge data, eg: instead of loading 40.000 nodes in one HTTP request, we could send 500/1000 nodes with several websocket server sent requests.

The solution that looks more suited for the job is Swampdragon. websocket-redis seems purposely limited and simplified.

At this stage it would be enough to do the following:

  • include swampdragon in nodeshot
  • find a way to send notifications to logged in users
  • update the notification UI when notifications are received
  • set good defaults for swampdragon in nodeshot.conf.settingsso that swampdragon can work out of the box in development and production
  • add instructions to the development and production install on how to run the websocket server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant