[aerogear-dev] Modularizing the Android Library
Summers Pittman
supittma at redhat.com
Wed Mar 5 10:35:35 EST 2014
On Wed 05 Mar 2014 10:32:49 AM EST, Matthias Wessendorf wrote:
>
>
>
> On Wed, Mar 5, 2014 at 4:29 PM, Daniel Passos <daniel at passos.me
> <mailto:daniel at passos.me>> wrote:
>
> I'd like add push in lib name
>
> aerogear-android-push (for core)
> aerogear-android-push-gcm
> aerogear-android-push-mqtt
>
>
> I still think that mqtt is more messaging, instead of push :-)
Well right now it would be "push" because we don't support
bidirectional communication. MQTT is just the transport.
We SHOULD investigate messaging soon since GCM supports it.
>
>
>
> -- Passos
>
>
>
> On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf
> <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>
>
>
>
> On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist
> <lholmqui at redhat.com <mailto:lholmqui at redhat.com>> wrote:
>
>
> On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf
> <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>
>>
>>
>>
>> On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman
>> <supittma at redhat.com <mailto:supittma at redhat.com>> wrote:
>>
>> Earlier in development (pre passos) making the
>> Android SDK into modules
>> was not a concern (in fact it was an anti-concern).
>>
>> Now, however, we have a much more complete project
>> and it is time to
>> have that discussion.
>>
>> Right now we have two BIG questions:
>>
>> 1) Do we want to break out interfaces and implementation?
>>
>> If we do this then we could reuse a lot of code to
>> make a aerogear-java
>> as well.
>>
>> 2) How granular do we want our modules?
>>
>> IE If we break out push into aerogear-android-push
>> would that include
>> GCM, SimplePush, MQTT, etc in one package or would it
>> look like
>>
>>
>> android-gcm
>> android-simplepush
>> android-mqtt
>
> +1 to those names, and i'm sure you mean aerogear-* :)
>
>
> yep ;-)
>
>
>>
>>
>>
>> aerogear-android-push-core,
>> aerogear-android-push-mqtt etc.
>>
>> Thoughts?
>>
>> --
>> Summers Pittman
>> >>Phone:404 941 4698
>> >>Java is my crack.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <mailto:aerogear-dev at 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
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <mailto:aerogear-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <mailto:aerogear-dev at 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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <mailto:aerogear-dev at 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
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
More information about the aerogear-dev
mailing list