On Tue, Feb 4, 2014 at 6:10 PM, Summers Pittman <supittma(a)redhat.com> wrote:
On 02/04/2014 11:52 AM, Matthias Wessendorf wrote:
On Tue, Feb 4, 2014 at 5:42 PM, Summers Pittman <supittma(a)redhat.com>wrote:
> On 02/04/2014 03:04 AM, Corinne Krych wrote:
> > Hello all,
> > I started doing demo app Buddies and Hobbies  (same idea than luke's
> one ). But instead of usin gcomplete separate chanel I wrapped Pipe
> within SyncPipe . Questions:
> > 1. looking at Luke's work I didn't see the usage of pipe at all.
> > 2. do we want to reuse Pipe protocol/interface for sync Pipe or use a
> different one?
> > I rather use the pipe underneath as we don't want to reimplement
> Paging, upload etc...
> > wdyt guys?
> I don't think extending Pipe is the best idea. However, I feel that any
> synchronizer should use pipes under the hood.
> Think composition over inheritance. Also overloading the read and save
> methods will get rather rough when we also have to check for conflicts
> and handle responses from the server.
> A SyncPipe could be the implementation the sync system works in iOS,
not sure I get this
Sorry was a merge error on my part when I was writing the email.
I meant that there isn't anything wrong with making a sync pipe for making
implementing sync on iOS easier. I just don't think it should be part of
Ah! ok :-)
At least it sounds like a good idea to leverage the pipes internally,
instead of making a AGSyncPipe
> I don't think it should be part of the spec/protocol.
> > With our actual server , we need adjust to serve REST endpoint. Ugly
> harcoded it (for now) to serve my purpose.
> > ++
> > Corinne
> > 
> >  https://github.com/lholmquist/ag-js-ds-poc
> >  https://github.com/corinnekrych/aerogear-sync-ios
> > 
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> aerogear-dev mailing list
aerogear-dev mailing list