Refactor multiform upload to better implementation and handle uploading large file. this will fix #24, #25, #27

[onikiri2007]

• Current multipart form upload implementation has the potential to run out of memory when uploading large files since it loads the whole file into memory and writes to the request file.
  this PR will attempt to fix that. code has been copied from Alamofire. their multiplatform data has a better implementation.

• Refactor example app to send the direct video/image path instead of copying and let the platform take care of the rest.

This should fix with issue #24, #25, #27

[ened]

@onikiri2007 - Before going into much detail: Have you considered depending on Alamofire instead of copying the code in? We can always strip out unused components on a release build, therefore I don't think package size is a major concern at the moment.

Also, good to not copy a requested file twice (in the example), and let the form builder be standardised. Will the Alamofire uploader make a copy of the request and store it in cache, though?

[onikiri2007]

@onikiri2007 - Before going into much detail: Have you considered depending on Alamofire instead of copying the code in? We can always strip out unused components on a release build, therefore I don't think package size is a major concern at the moment.
yeah that's a good idea. I'll change to make Alamorefire as dependency

Also, good to not copy a requested file twice (in the example), and let the form builder be standardised. Will the Alamofire uploader make a copy of the request and store it in cache, though? I'm not sure what you mean by this? Do you mean creating the request body as file? if this is the case, the answer is yes because urlsession only accept file as request body therefore It requires to create the one single file with all the files append. Alamofire's FormData class take care the better in this scenario.

[ened]

Also, good to not copy a requested file twice (in the example), and let the form builder be standardised. Will the Alamofire uploader make a copy of the request and store it in cache, though?

I'm not sure what you mean by this? Do you mean creating the request body as file? if this is the case, the answer is yes because urlsession only accept file as request body therefore It requires to create the one single file with all the files append. Alamofire's FormData class take care the better in this scenario.

OK, so it's only a code cleanup for the form data builder, sounds good!

[onikiri2007]

first one is done. Alamofire is now dependency. I might refactor the Urlsession part also later to use Alamofire's sessionManager instead. for now this will be first refactoring.

[ened]

@onikiri2007 , ok - just two things left from my point of view:

• please update the Podfile.lock (by running pod update)
• please try to run SwiftLint or similar to remove the whitespace changes (a lot of lines' only change is addition of white spaces)

We'll do SwiftLint on CI in the future as well.

[onikiri2007]

@onikiri2007 , ok - just two things left from my point of view:

• please update the Podfile.lock (by running pod update)
• please try to run SwiftLint or similar to remove the whitespace changes (a lot of lines' only change is addition of white spaces)

We'll do SwiftLint on CI in the future as well.

clean up is done
@ened Error: CocoaPods's specs repository is too out-of-date to satisfy dependencies. requires to update the podspec repo in CI

[ened]

@onikiri2007 please rebase

[ened]

Looks good. As mentioned we will add the Swift linter next.