Daemon A needs to push lots of data to Daemon B, which is located on another continent. The bandwidth available is usually quite high, but it's highly variable and might drop out entirely at times.
Is there an accepted "best strategy" for implementing this in Node? Does A just write as fast as it can to the socket and hope for the best? Should it detect errors and re-connect, resuming from the last offset that B successfully received? Does a socket ever become non-writeable? i.e. Does daemon A need to catch "socket not writeable" exceptions and throttle itself to suit the available bandwidth? I imagine some articles have been written on this topic, but I haven't found them yet. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
