On Fri, Oct 29, 2010 at 6:45 AM, Adriano Crestani <[email protected]> wrote: > The UI user should not care about where an album comes from, an > abstract layer needs to be created which will resolve file accessing > using some kind of AlbumAccessor implementation. Then, an accessor > would be required for each different photo provider. If we don't > abstract the album loading, it will get messy every time a new kind of > photo provider is added. > > My 2 cents :) >
Agree, User wise, and API wise, you want a collection of albums independent of where they are stored. Implementation wise, I was proposing that they become different sub trees on the repository and we have a AlbumAggregator which seems the same as your accessor that would know how to do any kind of delegation and would know how to provide a consistent view of all albums independent of it's type. Is this in sync with what you are suggesting ? -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
