Original report by Chris Billington (Bitbucket: 557058:cbf1bc43-1dc2-477b-9e25-1a8f40fd7ee3, GitHub: cbillington).
Would be good to allow a callback to be called in the case of failure to contact the zlock server. Most programs using zlock have no recourse but to fail if they can't contact the zlock server. It would be better if the programs could attach a callback so that they could say, hang while retrying instead, possibly displaying a modal GUI to show that this is happening so that you can go and fix your network if you want.
Or a GUI box asking "retry/ignore/fail" asking the user if they want zlock to retry, or to raise the exception to calling code, or to proceed at their own risk as if the lock acquisition was successful
Original report by Chris Billington (Bitbucket: 557058:cbf1bc43-1dc2-477b-9e25-1a8f40fd7ee3, GitHub: cbillington).
Would be good to allow a callback to be called in the case of failure to contact the zlock server. Most programs using zlock have no recourse but to fail if they can't contact the zlock server. It would be better if the programs could attach a callback so that they could say, hang while retrying instead, possibly displaying a modal GUI to show that this is happening so that you can go and fix your network if you want.
Or a GUI box asking "retry/ignore/fail" asking the user if they want zlock to retry, or to raise the exception to calling code, or to proceed at their own risk as if the lock acquisition was successful