[aerogear-dev] Multipart client thoughts

[Douglas Campos]

On Fri, May 10, 2013 at 03:38:44PM -0400, Summers Pittman wrote:
> 1.  There is no server side implementation / spec yet so the client
> "solution" should be rather pluggable.
+1
> 2.  I've only looked at iOS as a sanity check on my ideas.
This is the place where we would benefit from a side-to-side comparison
- we know it's doable (AFNetworking) but better safe than sorry.

> I've been working on some PoC's for multipart on Android.  After a
> few false starts here is the idea I've come up with to support
> multipart/from-data content types (ie uploading files).
> 
> Add a new configuration option to a Pipe's configuration: a request builder.
> 
> The request builder will be a callback/closure/class that consumes
> the data arguments from a pipes save request and produces the body
> of the request.  In Android it can be an interface which is
> implemented and in iOS it can be a block which is passed to
> AFHttpClient's multipartFormRequestWithMethod.  I'm not sure what
> the implications to JavaScript would be.
> 
> Specifically in Android the gson specific request code will be
> refactored into a GSONRequestBuilder, and we will write (and define
> the behavior of) a MultipartRequestBuilder.  Also
> PipeConfig.setGsonBuilder will become deprecated (a good move IMHO).
+1, we just need to make sure that this gets deprecated following the
semver rules (example: deprecate on 1.1.x, remove on 1.2.0)

-- 
qmx