Re: updates to proposal (was: Codebases and Tidbits and Moving towards a proposed vote)

> > 1. Allow those who want a different form of display to interact 
> with the WS.
> >  This would allow for really any additional type of interface to be written
> > (i.e. flex, ajax, etc.)
>
>Here, I think that Atom Feeds might be a good idea as well. See the
>concept described in [1]. We could even start doing gallery as a
>composition of multiple remote albums (e.g couple friends that took
>pictures from a given event and posted the pictures in different photo
>websites). Contradicting myself, and talking a little about
>technology, one good thing about Tuscany (and it's bindings) is that
>it makes you focus on the the business requirements/logic, and leave
>the communication infrastructure to a later point, so you have your
>service exposed as webservices, feeds or jsonRPC transparently.
>
>[1] http://www.google.com/uds/solutions/slideshow/

This may be what your last sentence above is saying.  Couldn't we 
expose the information as a Web service using Tuscany and then write 
something that would translate the info from the Web Service into a 
an Atom Feed?  That way, while it is a good idea, it can be dealt 
with at a later time?

> > 2. Allow other services to interact with the gallery.  The specific example
> > we were thinking of are the companies that allow you to order things with
> > photos on them.  We'd like to be able to allow interaction with these
> > services.
>
>I haven't looked into these services yet, but REST access to the
>pictures could give the same results.

Noel has more experience with these services than I do but from our 
discussion, I think that more information was needed at one time than 
what the REST interface would provide.

Angie