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

Extra doc #48

Open
fuson opened this issue Sep 26, 2014 · 3 comments
Open

Extra doc #48

fuson opened this issue Sep 26, 2014 · 3 comments

Comments

@fuson
Copy link

fuson commented Sep 26, 2014

What about to define behavior of the system when server is down (some exception or redeploy) and up after (for example by supervisor)?

@bombela
Copy link
Member

bombela commented Sep 26, 2014

thats outside the scope of zerorpc, up to you to implement it.

On Fri, Sep 26, 2014 at 9:52 AM, Aleksey Mihailiuk <[email protected]

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.

@fuson
Copy link
Author

fuson commented Sep 28, 2014

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.

@digitaldesigndj
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants