Add multi connection support #5
Conversation
smeinecke
commented
May 19, 2016
smeinecke
commented
- add connection pooling for each registry.
- add connection pooling for each registry.
|
Hmm, have to extend this a little more since it's unstable and does not handle new connections / login correctly - will update this once more. |
return login status after first run of worker.
fix some bugs in pool handling + shutdown.
Conflicts: package.json
|
Problems should be fixed now. Need to write some tests ;-) |
|
Cool, I'll merge it in once you've added some tests. |
|
Hey @smeinecke did you have anything you wanted to add to this? |
|
I might need to get this working with latest master unless you guys have a better approach? |
|
@chrisschaub I'm fine if you want to get this going in |
|
Oh nice. Any way to doc how you are using swarm or just post here? Are you
letting it manage connects to the rest server?
On Tue, Mar 7, 2017 at 12:24 PM William Travis Holton < ***@***.***> wrote:
@chrisschaub <https://github.com/chrisschaub> I'm fine if you want to get
this going in node-epp-server.js. I've moved to using node-epp-restful.js
and rabbit-epp.js more since I'm running this in Docker Swarm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADKssNMzqNY6TYRUc-VvXYtW3Ncdz5wdks5rjaD4gaJpZM4IiIql>
.
--
Christopher Schaub
http://chris.schaub.com
|
|
@chrisschaub I'm using swarm to scale the number of running instances that connect to the registry. I'm mainly using the rabbitmq version at the moment. This is kind of an experiment for a side project at work. |
3 participants
