Released Version 3.0

[Eric (Google)]

Just released version 3.0 of the API:
http://googledataapis.blogspot.com/2009/08/pdfs-revisions-folder-sharing-in.html

If you don't want to read the blog post...
Most notable are PDF upload/download, folder sharing, group/domain
level ACLs, and doc revisions.

Changelog: http://code.google.com/apis/documents/changelog.html#release-Version-3.0
Java guide: http://code.google.com/apis/documents/docs/3.0/developers_guide_java.html
Java sample: http://code.google.com/p/gdata-java-client/source/browse/trunk/java/sample/docs/

Expect other client libraries, samples, and developer guides will be
updated shortly.

Eric

[Graham Chiu]

PDF upload .. oooohhh .. cool.

--
Graham Chiu
http://www.synapsedirect.com
Synapse - the use from anywhere EMR.

[tazz_ben]

Eric -

I'm getting:

Content-Type application/pdf is not a valid input type.

When uploading a PDF (working with the protocol directly and this code
works with other types of documents)

On Aug 28, 4:32 pm, Graham Chiu <compkar...@gmail.com> wrote:
> PDF upload .. oooohhh .. cool.
>
>
>
>
>
> On Sat, Aug 29, 2009 at 11:30 AM, Eric (Google)<api.e...@google.com> wrote:
>
> > Just released version 3.0 of the API:

> >http://googledataapis.blogspot.com/2009/08/pdfs-revisions-folder-shar...

>
> > If you don't want to read the blog post...
> > Most notable are PDF upload/download, folder sharing, group/domain
> > level ACLs, and doc revisions.
>
> > Changelog:http://code.google.com/apis/documents/changelog.html#release-Version-3.0

> > Java guide:http://code.google.com/apis/documents/docs/3.0/developers_guide_java....
> > Java sample:http://code.google.com/p/gdata-java-client/source/browse/trunk/java/s...

>
> > Expect other client libraries, samples, and developer guides will be
> > updated shortly.
>
> > Eric
>
> --

> Graham Chiuhttp://www.synapsedirect.com

[tazz_ben]

Oh, is this not supported by the Google Apps version of Google Docs
yet? Is that the issue?

[Eric Bidelman]

Yep, Google Apps is supported. Two things to check:

1. Are you setting the GData-Version: 3 header 

    or using the ?v=3 URL query param?

2. Are you using the correct feed uri (they've changed)?

   POST /feeds/default/private/full

Eric

[tazz_ben]

Yeah, my bad, I looked at the change log not the new docs so didn't
see the addition of the version header. I've updated my uploader and
it works great.

Which brings up another question. I have other objects that interact
with the ACLs (with batches), and lists. I don't need any of the new
features in these areas, is there any reason to go through changing my
URLs and adding the new version header?

[Eric Bidelman]

The old URL formats won't work in v3.0 and PDF 

upload won't work in v < 3.0, so it's up to you if

PDF is worth it or not :)

Eric

[tazz_ben]

Eric -

Sorry, I should have been more clear. I'm using the 3.0 urls for
creating documents. However, given I use the protocol directly, I
have not updated the URLs for ACL interactions, lists, etc. What I
was trying to ask was if I don't need a feature in a particular
section is there any reason to upgrade? For instance, you also say in
your blog post that you've improved the latency of the API, was that
for 3.0 only? Also, (I'm trying to say this as politely as possible)
at times you post updates that break things for other people without
telling anyone. For instance, a while back you changed the uploader
so that it suddenly didn't accept files that didn't have an extension
on the name. And recently you changed the URLs on doc from Doc?id= to
Doc?docid= which broke part of my application logic until I found it
(also not placed in the change log). So my question is will the 2.0
version of the API become something that the team doesn't test. So
these sorts of things will happen even more if I stick on 2?

[Eric Bidelman]

V2 will be supported for a minimum of 3 years because the DocList API has graduated from labs: http://code.google.com/labs/

So, we will continue to support, fix issues, and test against v2, but new features/improvements will only be made to the latest version. BTW, the V3 launch marks the beginning of v2's deprecation.

I'm not sure about the undocumented changes you mentioned. The uploader?  Any changes to the API should be backwards compatible. 

That's more or less the guarantee of  the Labs badging.  As for the DocId issue, if you're constructing the link to the Google Docs manually...don't.

Always use what the API returns as the <link alt='alternate' href=''>.

Of course, nothing is perfect so we do roll out changes that break existing clients on occasion.  Those are usually

addressed as soon as some files an issue or posts on the forum.

Hope that helps,

Eric

[tazz_ben]

Eric-

Performance improvements question?

Also, sorry if I was unclear, the uploader issue was not in the 3.0
version and not to rehash history, but basically last year at some
point you (your group, whatever) decided to suddenly stop supporting
uploaded files where the slug didn't contain a file extension. So any
uploaded file with a defined type but just a name wouldn't work. This
is fixed now, but at the time having no idea why the files were
suddenly "randomly" failing (the error message rather un-descriptive)
and given I have two in production products; I spent some paniced
hours until I figured out what was happening. Anyhow, this was all in
the groups here (though I can't seem to find it), if I recall your
predecessor didn't know why it was failing either and did get it
changed back after I found the cause (but I had fixed it on my end at
the point anyway) . Anyhow, my big issue then was just communication,
not the change itself. (Sorry, you probably didn't want to know all
this)

I'm not building the URLs manually, but I do do horrible things to
your data at times because I use the API to do things like mail merges
(in one of my apps you can use an existing document as a "template"
and then merge a set of contacts against it creating a new, really
long, document where all of the variables in the doc were replaces
with the appropriate contact info -- like if you wanted to send out
christmas letters).

So the docid thing screwed up one of my regular expressions. Again,
just placing it in the change log would have solved the problem. And I
do realize that part of this is me because in your folks mind the API
is just to upload some stuff and migrate to Docs and I keep coming up
with ways to do things you didn't intend it for. But I have to think
other people would also appreciate a more complete change log.

[Eric Bidelman]

On Sun, Aug 30, 2009 at 1:58 PM, tazz_ben <b...@wbpsystems.com> wrote:

Eric-

Performance improvements question?

I think you might see small improvements in v2 and v1, but that's only because the versions share some of the same codebase.

The performance improvements that were made were intended for v3.0 only.

 

Also, sorry if I was unclear, the uploader issue was not in the 3.0
version and not to rehash history, but basically last year at some
point you (your group, whatever) decided to suddenly stop supporting
uploaded files where the slug didn't contain a file extension.  So any
uploaded file with a defined type but just a name wouldn't work.  This
is fixed now, but at the time having no idea why the files were
suddenly "randomly" failing  (the error message rather un-descriptive)
and given I have two in production products;  I spent some paniced
hours until I figured out what was happening.  Anyhow, this was all in
the groups here (though I can't seem to find it), if I recall your
predecessor didn't know why it was failing either  and did get it
changed back after I found the cause (but I had fixed it on my end at
the point anyway) .  Anyhow, my big issue then was just communication,
not the change itself. (Sorry, you probably didn't want to know all
this)

I think you're right.  This may have been before my time.

 

I'm not building the URLs manually, but I do do horrible things to
your data at times because I use the API to do things like mail merges
(in one of my apps you can use an existing document as a "template"
and then merge a set of contacts against it creating a new, really
long, document where all of the variables in the doc were replaces
with the appropriate contact info -- like if you wanted to send out
christmas letters).

So the docid thing screwed up one of my regular expressions.  Again,
just placing it in the change log would have solved the problem. And I
do realize that part of this is me because in your folks mind the API
is just to upload some stuff and migrate to Docs and I keep coming up
with ways to do things you didn't intend it for.  But I have to think
other people would also appreciate a more complete change log.

This may have been something that changed in Google Docs 

that we didn't know.  Again, it should have been transparent as 

far as the API is concerned but I completely understand that users

do complex things with the API(s).

[Mariano Mara]

On Aug 28, 8:30 pm, "Eric (Google)" <api.e...@google.com> wrote:
> Just released version 3.0 of the API:http://googledataapis.blogspot.com/2009/08/pdfs-revisions-folder-shar...

>
> If you don't want to read the blog post...
> Most notable are PDF upload/download, folder sharing, group/domain
> level ACLs, and doc revisions.
>
> Changelog:http://code.google.com/apis/documents/changelog.html#release-Version-3.0

> Java guide:http://code.google.com/apis/documents/docs/3.0/developers_guide_java....
> Java sample:http://code.google.com/p/gdata-java-client/source/browse/trunk/java/s...
>

> Expect other client libraries, samples, and developer guides will be
> updated shortly.
>
> Eric

Would be cool to know when you expect to release the python library
for version 3.0. I'm about to suggest at work to use google docs but I
work with python and it seems we're stuck at version 1.
I would appreciate any comments regarding this.
Mariano

[Eric (Google)]

Please follow this issue for v3.0 py updates:
http://code.google.com/p/gdata-python-client/issues/detail?id=261

[viatropos]

Sorry for the simple question, but how do I start using version 3.0
over version 2.0? I'm using the ruby gdata library and I don't see
the feedLink for revisions...

Thanks!

[Eric Bidelman]

Check out the DocList manager sample:

http://code.google.com/p/gdata-samples/source/browse/#svn/trunk/doclist/DocListManager

That uses v3.0: http://code.google.com/p/gdata-samples/source/browse/trunk/doclist/DocListManager/app/controllers/application.rb