Hi Matt, On Thu, Jun 21, 2018 at 6:25 AM Julian Reschke <[email protected]> wrote: > ...it would be helpful if you could link to example client code taking > advantage of this extension...
+1, ideally as readable test code that one can use as examples. >From the Sling clients perspective I'm interested in making this somewhat transparent, maybe something like: For downloads, a client requests http://my.sling.instance/somebinary.jpg and is redirected to https://somecloudprovider/23874623748623746234782634273846237846723864.jpg For uploads, it's a bit more complicated - maybe the client POSTing to Sling receives a 307 status with a JSON document that describes where/how to upload. In this case the client requires some knowledge of this new API, unless someone has a better idea. Do you see any obstacles in implementing something like this on top of your suggested API? -Bertrand
