On Fri, 7 Dec 2012, Jeroen van der Ham wrote:
The problem that I am trying to solve is the situation where the client is possibly behind a firewall/NAT/whatever, where the client is the only one capable of setting up a bidirectional TCP session. [snip]
In my opinion the simplest way to solve that is indeed to make the callback optional and allow clients to poll for updates. The reserveConfirmed may or may not be sent. But getting it failed to deliver would not trigger a fault.
Well, NSAs should already handle that (NSAs may be unavailable). Sure there will be some log entries. Clients can already poll, so I don't see how this would require any protocol changes. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet