Thanks for the reply @sklabnik!
I actually missed that there was an in-worker api, so thanks for the info Is there a performance benefit using this api or is it just a wrapper?
So if I understand correctly I need to list the keys to get the metadata which would be a separate call from fetching the value?
The way I thought it would work would be that the metadata would be added to a header of the response… This way I could return a 304 in the worker as soon as I get the response object which from my perspective would be a simple solution. It it’s only available I might as well keep the metadata in a separate entry and make two requests right?
I’m considering adding the metadata to the value and the reading the first chunk, which is the most efficient solution I can think of, but it does get a bit messy so I would rather not go ahead with it. Would be some much cleaner if we just could read and write headers