> On 14 Oct 2016, at 22:11, Eric Blake <[email protected]> wrote: > > Given that we have 4 years of buggy servers that will fail to react > correctly to NBD_OPT_GO and friends, is it worth enhancing the docs to > suggest that a robust client should be prepared for (buggy) servers that > mistakenly hang up after sending an NBD_OPT_ERR_UNSUP, and try > reconnecting to the server while avoiding the command that failed on the > previous run? Eventually, buggy servers will disappear, so we can't > mandate that clients take that extra step, but since it is a very common > problem at the present, it might help client implementations to be aware > of it. Then again, most client implementors read this list, so > documenting it in the protocol may be overkill.
I think the answer there is 'fix the server' rather than work around it in the client. -- Alex Bligh
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
