[aerogear-dev] Data-Sync: client-xmpp

Lucas Holmquist lholmqui at redhat.com
Fri Jan 16 09:37:13 EST 2015


> On Jan 16, 2015, at 9:20 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Fri, Jan 16, 2015 at 3:10 PM, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> 
> 
> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius <daniel.bevenius at gmail.com <mailto:daniel.bevenius at gmail.com>> wrote:
> Yeah, something needs to be done about this. Either moving it out, or having it only enabled with a profile (Summers mentioned this yesterday). 
> 
> -1 on profile.
> 
> IMO the goal is to create a sync client lib, similar to iOS (which is also on its own repo), so that should not be included on the java server. Eventually we should move out the JS bits as well 
> 
> https://issues.jboss.org/browse/AEROGEAR-1562 <https://issues.jboss.org/browse/AEROGEAR-1562>
> 
> For the JS part I am not sure what's the best way, since it's not just library, it's also demo

Currently the js-client is in a feature branch, https://github.com/aerogear/aerogear-js/tree/diff-sync-client <https://github.com/aerogear/aerogear-js/tree/diff-sync-client>

and the demo is also going into the js cookbook,  https://issues.jboss.org/browse/AGJS-268 <https://issues.jboss.org/browse/AGJS-268>
> 
>  
>  
> 
> 
> On 16 January 2015 at 15:01, Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>> wrote:
> Hi,
> 
> should we move the Android client-xmpp to its own repo? Right now, when building the server (and with an incomplete Android setup (aka new, clean repo)) you have to comment it out in order to build the server for running the JS demo.
> 
> IMO it would be nice if that gets moved out to something like "aerogear-android-xmpp-client".
> 
> Any thoughts?
> 
> -- 
> 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 <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 <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 <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 <http://twitter.com/mwessendorf>
> 
> 
> -- 
> 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 <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 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150116/e5f684ca/attachment-0001.html 


More information about the aerogear-dev mailing list