Add Expires support for OpenDAL

[Xuanwo]

Hi, OpenDAL currently doesn't support this. One possible approach might be to add Expires support, we can translate Expires to ttl internally for redis.

Originally posted by @Xuanwo in #5622 (comment)

---

Users can write data like op.write_with(key).expires(time).await.

[tisonkun]

How are Expires mapped to other services, e.g., S3?

[kaplanelad]

Thanks, @Xuanwo!
I'm planning to add Redis cache support to Loco.

[Xuanwo]

How are Expires mapped to other services, e.g., S3?

Expires is part of the HTTP standards, so S3 also supports Expires: https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html#API_PutObject_RequestSyntax

However, its behavior is related to client-side caching:

The date and time at which the object is no longer cacheable. For more information, see https://www.rfc-editor.org/rfc/rfc7234#section-5.3.

The HTTP Expires response header contains the date/time after which the response is considered expired in the context of HTTP caching.

[kaplanelad]

@Xuanwo I'd like to take this on.
Could you share your vision for the implementation? There is some example of this on another cache provider?

[kaplanelad]

@Xuanwo?

[Xuanwo]

Hi @kaplanelad, I have taken this feature into consideration for a while and think we can approve it this way.

Public API

op.write_with(path).expires(duration).await

Raw API

• Add expires: Duration in OpWrite.
• Add write_with_expires in Capability

At current time, we only need to support services that will really expire keys like redis and memcache.

And I feel like it's the time to implmenet redis support without the kv adapter. Many new features can be added in redis.