If these are DocList API questions you should be asking in this group:
http://groups.google.com/group/google-documents-list-api

 <http://groups.google.com/group/google-documents-list-api>Eric

On Tue, Oct 13, 2009 at 8:50 AM, Pascal <pascal.voitot....@gmail.com> wrote:

>
> Lately, I've been working a lot with google docs APIs also and I have
> also seen some weird behaviors. Sometimes it was my fault, sometimes
> it was due to some APIs evolutions linked to version changes (but the
> doc is not always reflecting those changes so it's not easy). But
> sometimes, something that was working perfectly suddenly ceased
> working with a "not very explicit" error and after a couple of hours,
> it worked again.
>
> I don't know what's the policy of google when they deliver new APIs
> versions but it appears their changes might have some side effects.
> It's a bit disturbing to work on a moving target and I would prefer a
> clearer view.
> Anyway, I really like those APIs ;)
>
>
>
> On Oct 12, 6:38 pm, Bill Berzinskas <b...@diffuseaudio.com> wrote:
> > I've been working on a wrapper for the Google Docs API for a few weeks
> > now, and it's been going well..  I have been having some SERIOUS
> > issues since friday however!
> >
> > 1) I initiate a call to create a document with no content, just a
> > title.  This return a 400 error stating "Could not convert
> > document."   This is wierd, because i'm not converting anything!
> >
> > 2) Retreiving a document, I do not get the content of the document,
> > rather I receive "Sorry, that file is corrupt, or an unknown
> > format."
> >
> > Thoughts?
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Docs Data APIs" group.
To post to this group, send email to Google-Docs-Data-APIs@googlegroups.com
To unsubscribe from this group, send email to 
google-docs-data-apis+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Docs-Data-APIs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to