Douglas Leite wrote:
After analyzing the Google Data API and the code of binding-atom,
binding-atom-abdera, and binding-feed, I propose an approach to start the
development of the GData biding.
I propose creating a new type of binding: biding-gdata. Similarly as
binding-atom-abdera, that extends the binding-atom, this new kind of binding
would extend the binding-atom too.
The implementation of the invokers (linke GetInvoker, PostInvoker, and
PutInvoker) would be done using the GData Java Client, that provides tools
and an abstract layer, abstracting the necessity of handling with HTTP
requests/responses and XML's processing.
The binding-gdata could extend the binding-rss aiming to allow RSS feeds.
This approach looks like the binding-feed, but reusing the binding-atom and
binding-rss, and using the GData Java Client to implement the invokers.
What do you think about?
Douglas,
We need to take some care over the idea of using the GData Java Client - we need to check out the
legal terms that apply to the client code, since it does not appear to have a license that is
compatible with the Apache open source license, as far as I can tell.
I'm not saying that you can't use the Google code, but we do need to ask to see what the right way
would be to use this code.
Yours, Mike.
