3
storage createSignedUrl / createSignedUrls speedup
Source: supabase/supabase#28692 · opened by @gc-ft
Hi, the storage API's createSignedUrls interface is relatively "slow". For just a handful of Urls to sign it takes over half a second. In today's age of fast responding websites I would consider this slow. After checking the code there seems to be a rather simple "speedup" fix, at least as an optional variable to the API calls: For both a single object and for the multiple objects at once setup the system will verify that the objects in question exist and only then build a signed url. This process does not use anything from the findObject / findObjects calls, actually signObjectUrl depends on the findObject call to throw NoSuchKey error if objects are not found to stop the process since it is not caught in signObjectUrl. I understand why this seems beneficial to do, however, if I am SURE that my objects exist (because I checked before) or similar reasons, why even check if they are there? Later on when the signed url is called to actually load…
No pledges yet. Be the first to back this.
Comments
Similar requests
Way to createSignedUrls with image transformation
7 votes · 0 comments
createSignedUrls should allow for storage transformations per image in the same was createSignedUrl does
1 vote · 0 comments
Add support for image transformations in bulk storage URL signing (getSignedUrls)
2 votes · 0 comments
[storage-js] Skip `.from('bucket')` storage calls syntax for `createSignedUrls` function
1 vote · 0 comments
Add Storage Adapter For Chrome.Local.Storage Api
3 votes · 0 comments
No comments yet.