On Tue, Oct 12, 2010 at 1:00 AM, Luciano Resende <[email protected]>wrote:
> On Mon, Oct 11, 2010 at 12:17 PM, Avdhesh Yadav <[email protected]> > wrote: > > > > I am Thinking of one use case.Lets say user wants to subscribe a remote > > album(e.g flicker).He adds a feedurl and clicks to subscribe button.Now > we > > have two options. > > > > - One we immediately fetch the meta data from the feedurl(name,titile, > > location) etc and save it to jcr repository.When user wants to view the > > album we fetch remote album meta data from our local JCR and display > them.I > > think performance wise it beneficial but we have to sync our repo > > frequently. > > > > - Another option is that we only save the feedurl to our jcr repository > > initially and only fetch the meta data when user actually wants to view > the > > remote album.The benefit of this approach is that we do not need to > > frequently sync our jcr. > > > > Thoughts ? > > I'd say that we would want to let the user specify title, and the URL > of the remote album. > > As for storing stuff locally in our JCR repo and fetching it all the > time, we should have metadata stored locally to allow searching. > > As for how we go about approaching this, I'd recommend that we start > with retrieving it from the remote site and storing in a local cache > (e.g a map) inside of a @Scope("COMPOSITE") component, and then on a > second phase, we would add the full blow sync and test searching, etc. > > Thoughts ? > Yes its good idea to develop this functonality in small increments.+1 I thinking of following data structure for the local cache. Map<String,List<Image> cache = new HashMap<String, List<image>(); cache.put("title", remoteImages); > -- > Luciano Resende > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > -- Avdhesh Yadav http://www.avdheshyadav.com http://twitter.com/yadavavdhesh
