Swift API v2 Example of uploading a file using filesUploadSession(Start, Append, Finish)

Is there a reason why filesUploadSessionAppend takes an offset and Session ID and filesUploadSessionFinish takes a Files.UploadSessionCursor which wraps the Offset and Session ID ?

Seems like these calls should hava a similar calling convention except that SessionFinsish should have the extra  CommitInfo

Actually I think the API would be cleaner with a smple

   SessionStart -- NO Data just return the SessonID

   SessionAppend   Args would be SessionID, Data, and Offset

   SessionFinish     Args would be SessionID and Completion

Adding a data transfer to the SessionStart and SessionFinish makes the interface much more clunky ... and all you have saved is possibly one small packet transfer. You Currently need minimally 2 requests (Start and Finish), one can be small. With a cleaner interface you would need minimally 3 requests, two are small.