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.

Sign up for GitHub

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

Jump to bottom

Outbound connection pool for Websockets #10

Open
xaviervia opened this issue Feb 8, 2013 · 1 comment
Open

Outbound connection pool for Websockets #10

xaviervia opened this issue Feb 8, 2013 · 1 comment
Assignees
@xaviervia
Labels
enhancement
Milestone
Reusable connections

Comments

@xaviervia
Copy link
Contributor

Currently, a websocket client connection is opened and closed for every Dispatch to a inbound websocket JSTP node. The proposal is to optimize by pooling outbound connections and persisting them.
@ghost ghost assigned xaviervia Feb 8, 2013
@xaviervia
Copy link
Contributor Author

It seems that the main issue here is to escape the EventMachine's event loop in order to be able to continue processing in the client. A suggestion that looks promising is to run EventMachine in a thread.

@xaviervia xaviervia reopened this Mar 14, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xaviervia xaviervia

Labels
enhancement
Projects
None yet
Milestone
Reusable connections
Development

No branches or pull requests
1 participant
@xaviervia