In our previous release, we had the ability to subscribe/reference to
external photos using Tuscany references (see composite below)
Although that works fine, the user experience is not so dynamic, as
the user needs to update the composite and then re-deploy the
application.
<component name="AlbumAgregator">
<implementation.java class="services.AlbumAgregator"/>
<service name="Album">
<t:binding.jsonrpc/>
</service>
<reference name="album" target="Album"/>
<reference name="albumFeed">
<t:binding.atom
uri="http://api.flickr.com/services/feeds/photoset.gne?set=72157601530865813&nsid=36437...@n00&lang=en-us"/>
</reference>
</component>
Going forward, I would like to have a more flexible user experience
here, where a user could go to the admin ui and create a new album of
type subscription and provided the right URL for the remote album. In
order to have this user experience working, we will need to provide
local album implementations that would provide similar functionality
offered by the Tuscany ATOM, GDATA bindings and would understand the
formats of the external feeds to extract album/image information from
it. This is the ideas I had when I created photark-18 and photark-19
jiras and I guess that, them combined (with possible other album
types) + plus support for admin ui could be a great GSoC project.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
