planning to upgrade (smoothly, I hope) from version 2 to 3

[Patricia Goldweic]

Hi,

I have a few questions as I prepare to upgrade a production app from version 2 to 3:

- Is 2-legged OAuth authentication supported in this version? (I have seen some posts indicating trouble with OAuth)

- Are permissions placed with version 2 of the apis visible by the version 3 api calls?

- Can I simply change the urls I've been using to retrieve documents and expect that things will work in the same way? (possibly converting them to https urls)

- Can I continue retrieving the acl feed of a document, spreadsheet and form, given a document id? (I'd like to avoid having to retrieve the document first, or even worse, the list of all documents, until I find the relevant document, and then in turn find its acl feed url?). For version 2, I've been using the following urls to retrieve acl feeds:

    - documents:  http://docs.google.com/feeds/acl/private/full/document%3A" + docId

    - spreadsheets: http://docs.google.com/feeds/acl/private/full/spreadsheet%3A" + result

What are the corresponding urls for version 3? Also, what is the corresponding acl feed url for a folder?

- Is version 3 of the library still in 'Lab' mode, and does this mean that there's no guarantee from Google that apis won't change in the near future? Is this considered a safe version for a production app to use?

 

Thanks in advance for helping me answer these important questions!

-patriciaG

[James F]

I upgraded to 3 and now I am thinking of going back. It is very
frustrating to keep trying to work around the OAuth problems.

I don't know maybe there is something I am missing and there is no
documentation about the missing OAuth. Most things I have found work
arounds for but there are others that I just can't do.

[Eric (Google)]

Hi Patricia,

On Nov 24, 5:50 pm, "Patricia Goldweic" <pgoldw...@northwestern.edu>
wrote:

> Hi,
> I have a few questions as I prepare to upgrade a production app from version
> 2 to 3:
> - Is 2-legged OAuth authentication supported in this version? (I have seen
> some posts indicating trouble with OAuth)

It is. AFAICT, those posts are developer issues.

> - Are permissions placed with version 2 of the apis visible by the version 3
> api calls?

Yes. Permissions are ultimately store withing Google Docs
and have nothing to do with which API version is used to change them.

> - Can I simply change the urls I've been using to retrieve documents and
> expect that things will work in the same way? (possibly converting them to
> https urls)

More or less, yes. v3.0 URIs are also little more user friendly.

> - Can I continue retrieving the acl feed of a document, spreadsheet and
> form, given a document id? (I'd like to avoid having to retrieve the
> document first, or even worse, the list of all documents, until I find the
> relevant document, and then in turn find its acl feed url?). For version 2,
> I've been using the following urls to retrieve acl feeds:
>     - documents:  http://docs.google.com/feeds/acl/private/full/document%3A"
> + docId
>     - spreadsheets:http://docs.google.com/feeds/acl/private/full/spreadsheet%3A" + result

Yes. In v3.0 it's:
/feeds/default/private/full/document%3A1234/acl

> What are the corresponding urls for version 3? Also, what is the
> corresponding acl feed url for a folder?

URIs are listed in the reference guide:
http://code.google.com/apis/documents/docs/3.0/reference.html

Accessing a folder's acl feed is the same as the other types:
/feeds/default/private/full/folder%3A1234/acl

> - Is version 3 of the library still in 'Lab' mode, and does this mean that
> there's no guarantee from Google that apis won't change in the near future?

Yes, v3.0 (of the API) is still in labs but we'll be taking it out
soon.
FWIW, we have not changed functionality in v3.0 since it launched
in August, only added features.

> Is this considered a safe version for a production app to use?

Yes. It's faster and more stable than previous versions. It takes
a while to get out of labs, but that doesn't mean the version is
less worth.

[Patricia Goldweic]

Thanks so much for your response Eric!. That was extremely helpful,
-Patricia
pgol...@northwestern.edu

[Eric (Google)]

@James

You're working with a number of complex
technologies (OAuth (2LO), the Java client library, etc.) that
have nothing to do with the Documents List API v3.0.

Please continue to post any questions you have
regarding OAuth and using it with the DocList API
and I'll try and help/debug as best as I can.

_If_ there something that worked for you in v2.0
that does not work in v3.0, please let me know.
It's also possible that the Java lib had a regression
somewhere, but I haven't seen anyone post a
complaint besides yourself.

Eric

[James F]

Thank you Eric, I am not sure what is going on. It could very well be
me.
I tried loading up a 2.0 lib and that did not work so I don't think it
is version specific anymore.
Everything works fine from a client sign in perspective I only have
problems with 2LO. I like that 2-leg OAuth has an acronym.
I will keep looking at it from different angles and see if I can set
up a sniffer to read the posts as the go to the server.