Hi,
I think this only covers the case when client side completely restarts/recreates the GF Pool to the server. But what about the case where:
1. Client was connected
2. Client lost connectivity for longer than durable timeout
3. GF will retry connecting back to the system automatically
4. Eventually GF reconnects back (let's say after durability expired on server side), but it's all kind of transparent to the user of GF client API right?
So, not sure how in that case client would know that there is an entry expected from server. Client would have to be able to detect connection loss and then connection reconnect and check for that durability event.