GData and Seaside

Hi,

At heart, Google Data APIs use Atom feeds and entries (XML) as a data
format and HTTP as a protocol for data transmission - extending the
Atom Publishing Protocol.
http://code.google.com/apis/gdata/index.html
http://code.google.com/apis/gdata/overview.html

Does somebody have used some API google provide in conjonction with seaside ?

I'm thinking especially to those of calendar, contact and also all the
common elements (http://code.google.com/apis/gdata/elements.html) and
OAuth (http://code.google.com/apis/gdata/articles/oauth.html)

If not, I'll give a try in the next monthes (I think 2009/02) and of
course, I'm open to all suggestion.

I don't know if it's better to use seaside internal request handler or
use direct http request processing. I've found several interesting
links:
-using gdata with ruby
(http://code.google.com/apis/gdata/articles/using_ruby.html)
-using gdata with curl
(http://code.google.com/apis/gdata/articles/using_cURL.html)
-...

Maybe, another direction is to port the java client that already
exists (http://code.google.com/p/gdata-java-client/
http://code.google.com/p/gdata-java-client/source/browse/#svn/trunk/java/src/com/google/gdata)

Thanks in advance for any information.

--
Cédrick

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2008/11/27 Cédrick Béler <[hidden email]>: +1
Make your custom request hander / entry point subclass.

Cheers
Philippe

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside