On Sun, Jan 30, 2011 at 7:04 PM, Subash Chaturanga <[email protected]> wrote: >> >> You should think separation of concerns here. The specific modules >> that deal with remote albums (subscriptions) should know how to handle >> the specifics of the album providers (e.g picasa, flickr, etc). Then >> we can have a subscription manager in the JCR repository that, once >> you create a new subscription will use that provider specific >> component to read the remote album and store locally, and not the >> other way around, where the provider would store data in the JCR. > > > +1 , will do. > > Because currently I have two provider specific service components which do > both read and store albums in JCR, by themselves and UI talks to them > separately. So adding a subscription manager and UI will only call to that > manager and he will read the albums from a provider and store them. I hope I > got your idea correctly. > >
Looks like we are in the same page. BTW, I'm trying to get the same services in place in the REST branch, hopefully I can get that in the next day or so and it might be of some help. -- Luciano Resende
