GTMSessionUploadFetcher uses different resumable upload protocol respect to GTMHTTPUploadFetcher

[Diego Negri]

I can see GTMSessionUploadFetcher supports a 'different' resumable upload protocol than GTMHTTPFetcher. 

GTMSessionUploadFetcher uses 'X-Goog-...' headers respect to the 'X-Upload-Content-Type'/'X-Upload-Content-Lenght' used in GTMHTTPFetcher and documented as 'Google Resumable Protocol'.

Will the 'old' resumable protocol supported in the future ? or is there public documentation for the new one ?

Thx

Diego

[Greg Robbins]

The "old" resumable upload protocol is widely used by clients, so I expect it will be around for a while. Server teams careful monitor usage to understand how much an API is currently being relied upon, and deprecation is based on careful consideration of that analysis.

The "new" protocol still needs to be publicly documented, unfortunately. Google has an open internal bug number for that, b/12990896