Extra doc
fuson opened this issue · 3 comments
What about to define behavior of the system when server is down (some exception or redeploy) and up after (for example by supervisor)?
thats outside the scope of zerorpc, up to you to implement it.
On Fri, Sep 26, 2014 at 9:52 AM, Aleksey Mihailiuk <notifications@github.com
wrote:
What about to define behavior of the system when server is down (some
exception or redeploy) and up after (for example by supervisor)?—
Reply to this email directly or view it on GitHub
#48.
I was not talking about the implementation, it just a hint for readme content. As for me some information about zeromq "sockets" and it is not necessary to implement reconnect logic would be useful and may be the argument to chose this module.
Where is the scope of zeroRPC defined? I need this for my app. Okay, not really, but my app might need this someday. I know that I need to start both apps in 30s or less, but those fucking noobs... the ones that I'm trying to help with my software. Well, god help us all... Dumber than I was 5 years ago; At least.
@fuson 👍
@bombela Awesome Software! I got the node blinkylights working with the libnfc and python talking to the LCD. Thank You!
OSS FTW: https://github.com/digitaldesigndj/node-nfc-poll/blob/master/lcd.py