Thanks for the feedback, Antoine. That would be a natural method to have - then the server could deny uploads (as you mention) or note that the stream already exists. I've updated the proposal to reflect that, leaving more detailed semantics (e.g. append vs overwrite) application-defined.
Best, David On 7/25/19, Antoine Pitrou <anto...@python.org> wrote: > > Le 08/07/2019 à 16:33, David Li a écrit : >> Hi all, >> >> I've put together two more proposals for Flight, motivated by projects >> we've been working on. I'd appreciate any comments on the >> design/reasoning; I'm already working on the implementation, alongside >> some other improvements to Flight. >> >> The first is to modify the DoPut call to follow the same request >> pattern as DoGet. This is a format change and would require a vote. >> >> https://docs.google.com/document/d/1hrwxNwPU1aOD_1ciRUOaGeUCyXYOmu6IxxCfY6Stj6w/edit?usp=sharing > > It seems it would be useful to introduce a GetPutInfo (or GetUploadInfo) > so as to allow differential behaviour between getting and putting. > > (one trivial case would be to disallow uploading altogether :-))) > > Regards > > Antoine. >
