9:38 p.m.
First a few caveats:
1. There is no server side implementation / spec yet so the client
"solution" should be rather pluggable.
2. I've only looked at iOS as a sanity check on my ideas.
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).
wdyt?
Summers
10:08 p.m.
I have to think on this. The simple answer for JS is XMLHttpRequest2 but since 3 of our
supported browsers don't support it (THANKS IE9, iOS Safari 4.3 and Android 2.3!), I
have to come up with something else which will likely not be pretty.
On May 10, 2013, at 2:38 PM, Summers Pittman <supittma(a)redhat.com> wrote:
First a few caveats:
1. There is no server side implementation / spec yet so the client "solution"
should be rather pluggable.
2. I've only looked at iOS as a sanity check on my ideas.
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).
wdyt?
Summers
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
9:04 a.m.
sounds good so far!
On Fri, May 10, 2013 at 9:38 PM, Summers Pittman <supittma(a)redhat.com>wrote:
First a few caveats:
1. There is no server side implementation / spec yet so the client
"solution" should be rather pluggable.
yeah, nothing in Controller, but anything that supports multipart/upload
(e.g. JAX-RS/RestEasy) should be able to consume the uploaded files;
2. I've only looked at iOS as a sanity check on my ideas.
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).
wdyt?
Summers
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
5:17 a.m.
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
6:39 p.m.
Here is a before/after gist for the things I will need to change to put
in the Builders I was referring too.
https://gist.github.com/secondsun/5fa7ddd46c76b03b723e
And a comparison for discussion:
https://github.com/aerogear/aerogear-android/compare/multipart
On 05/10/2013 03:38 PM, Summers Pittman wrote:
First a few caveats:
1. There is no server side implementation / spec yet so the client
"solution" should be rather pluggable.
2. I've only looked at iOS as a sanity check on my ideas.
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).
wdyt?
Summers
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
3:51 p.m.
+1 to PipeConfig.setGsonBuilder will become deprecated
Comments on commits
On Wed, May 15, 2013 at 1:39 PM, Summers Pittman <supittma(a)redhat.com>wrote:
Here is a before/after gist for the things I will need to change to
put
in the Builders I was referring too.
https://gist.github.com/secondsun/5fa7ddd46c76b03b723e
And a comparison for discussion:
https://github.com/aerogear/aerogear-android/compare/multipart
On 05/10/2013 03:38 PM, Summers Pittman wrote:
First a few caveats:
1. There is no server side implementation / spec yet so the client
"solution" should be rather pluggable.
2. I've only looked at iOS as a sanity check on my ideas.
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).
wdyt?
Summers
_______________________________________________
aerogear-dev mailing
listaerogear-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
11:50 a.m.
Hi,
can I propose to start a page that lists how Android multipart upload will look like (e.g.
with MultipartRequestBuilder). I would like to have a view first and will go ahead and
add iOS for comparison.
Also a question i have for this is monitoring the progress of uploading. In iOS you can
specify a block to be executed during the uploading that reports periodically the bytes
uploaded etc so we can easily hook a user defined block. How we will approach this?
Thanks
Christos
On May 16, 2013, at 4:51 PM, Daniel Passos <daniel(a)passos.me> wrote:
+1 to PipeConfig.setGsonBuilder will become deprecated
Comments on commits
On Wed, May 15, 2013 at 1:39 PM, Summers Pittman <supittma(a)redhat.com> wrote:
Here is a before/after gist for the things I will need to change to put in the Builders I
was referring too.
https://gist.github.com/secondsun/5fa7ddd46c76b03b723e
And a comparison for discussion:
https://github.com/aerogear/aerogear-android/compare/multipart
On 05/10/2013 03:38 PM, Summers Pittman wrote:
>
> First a few caveats:
>
> 1. There is no server side implementation / spec yet so the client
"solution" should be rather pluggable.
> 2. I've only looked at iOS as a sanity check on my ideas.
>
> 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).
>
> wdyt?
>
> Summers
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
3990
days inactive
4004
days old
6 comments
6 participants
participants (6)
-
Christos Vasilakis -
Daniel Passos -
Douglas Campos -
Kris Borchers -
Matthias Wessendorf -
Summers Pittman