Re: [aerogear-dev] Modularizing the Android Library

On Wed, Mar 5, 2014 at 5:01 PM, Summers Pittman <supittma(a)redhat.com&gt; wrote: On Wed 05 Mar 2014 10:58:45 AM EST, Matthias Wessendorf wrote: On Wed, Mar 5, 2014 at 4:35 PM, Summers Pittman <supittma(a)redhat.com <mailto:supittma@redhat.com>> wrote: 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(a)passos.me <mailto:daniel@passos.me> <mailto:daniel@passos.me <mailto:daniel@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. and that's different from push (think APNs / SimplePush), which is what we support on the UnifiedPush Server. Right. mqtt and friends were just examples of things we had talked about. However messaging for the project may be something we look at one day. agreed

doing messaging, via GCM, is fine but something different. There the underlying technology (e.g. MQTT vs. GCM) is really just a transport, like: -messaging-gcm -messaging-mqtt -messaging-stomp -M -- Passos On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf <matzew(a)apache.org <mailto:matzew@apache.org> <mailto:matzew@apache.org <mailto:matzew@apache.org>>> wrote: On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist <lholmqui(a)redhat.com <mailto:lholmqui@redhat.com> <mailto:lholmqui@redhat.com <mailto:lholmqui@redhat.com>>> wrote: On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf <matzew(a)apache.org <mailto:matzew@apache.org> <mailto:matzew@apache.org <mailto:matzew@apache.org>>> wrote: On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman <supittma(a)redhat.com <mailto:supittma@redhat.com> <mailto:supittma@redhat.com <mailto:supittma@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(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> <mailto:aerogear-dev@lists.__jboss.org <mailto:aerogear-dev@lists.jboss.org>> https://lists.jboss.org/__mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev> -- Matthias Wessendorf blog: http://matthiaswessendorf.__wordpress.com/ <http://matthiaswessendorf.wordpress.com/> sessions: http://www.slideshare.net/__mwessendorf <http://www.slideshare.net/mwessendorf> twitter: http://twitter.com/mwessendorf _________________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> <mailto:aerogear-dev@lists.__jboss.org <mailto:aerogear-dev@lists.jboss.org>> https://lists.jboss.org/__mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev> _________________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> <mailto:aerogear-dev@lists.__jboss.org <mailto:aerogear-dev@lists.jboss.org>> https://lists.jboss.org/__mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev> -- Matthias Wessendorf blog: http://matthiaswessendorf.__wordpress.com/ <http://matthiaswessendorf.wordpress.com/> sessions: http://www.slideshare.net/__mwessendorf <http://www.slideshare.net/mwessendorf> twitter: http://twitter.com/mwessendorf _________________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> <mailto:aerogear-dev@lists.__jboss.org <mailto:aerogear-dev@lists.jboss.org>> https://lists.jboss.org/__mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev> _________________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> <mailto:aerogear-dev@lists.__jboss.org <mailto:aerogear-dev@lists.jboss.org>> https://lists.jboss.org/__mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev> -- Matthias Wessendorf blog: http://matthiaswessendorf.__wordpress.com/ <http://matthiaswessendorf.wordpress.com/> sessions: http://www.slideshare.net/__mwessendorf <http://www.slideshare.net/mwessendorf> twitter: http://twitter.com/mwessendorf _________________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> https://lists.jboss.org/__mailman/listinfo/aerogear-dev <https://lists.jboss.org/mailman/listinfo/aerogear-dev> -- Summers Pittman Phone:404 941 4698 Java is my crack. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Summers Pittman Phone:404 941 4698 Java is my crack. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev