Hi, On 10.07.17, 11:18, "Bertrand Delacretaz" <[email protected]> wrote: > Throw an exception maybe? BinaryNotAvailableAtThisTime, including an > ETA for availability. The application can then decide how to handle > that.
Bertrand, this is exactly what I have suggested in two previous mails: My concrete suggestion would be, as I wrote: if it's in cold storage, throw an exception saying so, and load the binary into hot storage. A few minutes later, re-reading will not throw an exception as it's in hot storage. So, there is no API change needed, except for a new exception class (subclass of RepositoryException). An application can catch those exceptions and deal with them in a special way (write that the binary is not currently available). Possibly the new exception could have a method "doNotMoveBinary()" in case moving is not needed, but by default the binary should be moved, so that old applications don't have to be changed at all (backward compatibility). Regards, Thomas
