Slightly extend `base` interface for stateless programs about blazer HOT 4 CLOSED

Hi Paweł, thanks for opening a ticket. So that I'm clear, the scenario is that a modification to the contents of B2 could be made that is not identifiable in blazer? I'm not against exposing base.File.id but I feel like this is something that could be handled better by e.g. relisting unfinished files.

I'd like to see a code snippit that benefits from this, if possible? Thanks.

from blazer.

listing unfinished files is not free: it's a "C" transaction, limited to 2500 free calls per day, so I'd rather avoid a double call

from blazer.

If we consider a http server, it could serve something like this:

GET /listUnfinishedFiles?bucketId=abcdef

Which could return a list of objects, in json or something.

But then how should the request for cancelling a large fine upload look like?

POST /cancelLargeFileUpload
bucketId=abcdef&fileId=ac4ef79a16d38b4c2d80

Seems like a natural solution. Since B2 allows multiple large file uploads of the same filename to exist, providing a functionality of cancelling user-selected large file upload session would be very messy without the fileId.

from blazer.

@kurin you asked for snippet that benefits from this change - here is WIP commit in minio/minio to switch from their fork (minio/blazer) to this repo - mzukowski-reef/minio@c455ad3 - you can see there changes required in minio code to support changes in code commited in PR #65 as well as how kurin/blazer/base is used in minio code

from blazer.