@paoloardoino hi, nice project! Take a look at http://pjanuario.github.io/zmq-service-suite-specs/ … is quite similar!
-
-
Replying to @prnjanuario
@prnjanuario I had a quick look to your code. Don't see any broker queue manager that handles busy workers. Which solution are you using?1 reply 0 retweets 0 likes -
Replying to @paoloardoino
@paoloardoino the broker executes a round robin distribution and the workers need to send a keep alive every 1s. so if they are busy..1 reply 0 retweets 0 likes -
Replying to @prnjanuario
@paoloardoino they willn't send keep alive & they will be removed as available workers. This solution have some good&less good side effects.1 reply 0 retweets 0 likes -
Replying to @prnjanuario
@prnjanuario I'm following the MDP 0.2 specs using a Broker level request queue2 replies 0 retweets 0 likes -
Replying to @paoloardoino
@paoloardoino it seems the only reason for it. Am I wrong? How are you handling clients disconnection?3 replies 0 retweets 0 likes -
Replying to @prnjanuario
@prnjanuario what do you think about this solution? We should collaborate1 reply 0 retweets 0 likes -
Replying to @paoloardoino
@paoloardoino At the moment I am not handling client disconnections and didn't think on a solution for that yet.1 reply 0 retweets 0 likes -
Replying to @prnjanuario
@paoloardoino I was trying to find a way to expire messages in zeromq, http://goo.gl/PLdQg62 replies 0 retweets 0 likes -
Replying to @prnjanuario
@paoloardoino Collaboration is always good :) what do you have in mind?3 replies 0 retweets 0 likes
@prnjanuario that has expiration integrated for saved key/values. Using client acknowledge I can track if a client has received a message
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.