forked from TrueCloudLab/frostfs-sdk-go
a86c08b3ee
Based on the applications that use pool, most of them simply set session token duration to MaxUint64 value. It is completely understandable, because epochs are incrementing and expiration value will be surpassed sooner or later, unless it is MaxUint64. As an alternative I suggest specifying duration instead of absolute epoch values. Now apps can set duration of 100-200 epochs and pool automatically calculated expiration epoch base on the network info. Signed-off-by: Alex Vanin <alexey@nspcc.ru> |
||
---|---|---|
.. | ||
cache.go | ||
key.go | ||
mock_test.go | ||
pool.go | ||
pool_test.go | ||
sampler.go | ||
sampler_test.go |