nbspou / dospace Goto Github PK

• String downloadText()
  • This would verify if content-type starts with text/
• downloadImage()
  • This would verify if content-type starts with image/
• downloadFile()
• uploadText(String text)
• (uploadImage?)
• uploadFile

Library should handle everything behind the scenes.

We also want a mechanism for pre-signing both uploads and downloads in the style of new Bucket.signed(string endpointUrl, string key, Map<String, String> signatureHeaders) as specified by issue #1.

How to use presigned url to upload?

Instead of making separate client objects for the spaces server and buckets, have a separate Spaces client and Bucket client. The Spaces client should have a function to create the Bucket client, and adjust the endpoint Uri accordingly. It should still be possible for the user to create the Bucket client directly.

Hello,

can you update the xml dependency? Because it causes problems with other libraries that use a high version of xml.

Thanks

Setting Cache-control metadata to bucket.uploadFile gets overwritten /updated as custom metadata.

e.g. Map<String, String> metadata = {'Cache-Control':'public'}
String etag = await bucket.uploadFile(
objectKey, File(filePath), lookupMimeType(filePath), dospace.Permissions.public,meta: metadata);

uploads with the metadata as x-amz-meta-cache-control. dospace_bucket.dart overrides the metadata value always with x-amz

Hi,

Your xml dependency is very outdated and is clashing with other packages. Plz consider upgrading it. Have also raised a PR for the same.

Thanks

I am trying to upload File instance from 'dart:html' but this library is not able to upload the files. I have tried multiple things, like converted file instance to Uint8List also

The client app will send to the server the filetype, filesize, and sha256 hash of the file which it needs to upload. In general these files will be images. It may be nice to let the library generate the options, if it proves useful and practical.

After validating the received options, the server will generate the key for the file in the storage bucket, store this key with the user's account in the database, and then use the library to generate the signed HTTP request to upload the data. The request headers and options are then sent to the client app.

Using the pre-signed HTTP request from the server, the client will upload the file, and notify the server when it is finished. The library is used to handle the upload properly with the pre-signed request.

Handling failed or non-uploaded files and other database cleanup is up to the server, and not a concern here.

hey guys,

any plans to update to null safety?

Attached is the error i'm getting, all the keys are double checked but still experiencing this issue, What could be the cause?
Im using dospace: ^0.11.10,

List maxKeys should actually limit and additional requestMaxKeys field should limit per request

This package needs to update xml and http dependencies