geremyk / google-gdata

Automatically exported from code.google.com/p/google-gdata
0 stars 0 forks source link

atomfeedentry.ReadOnly is not valid for DocumentList Documents #210

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Share a Viewer only status document doc with Person B
2. Open Person B's document list
3. when atomfeedentry.ReadOnly flag for tha document doc entry

What is the expected output? What do you see instead?
atomfeedentry.ReadOnly is based on the existance of an edit link entry. An 
edit link entry is included in the feed.

<link rel = "edit" type = "application/atom+xml" href = 
"http://docs.google.com/feeds/documents/private/full/document%3Adg8zqnff_34
0xyzzcr/fq9zyz5l"/>

What version of the product are you using? On what operating system?
.Net client 1.3.1.0

Please provide any additional information below.
There's a larger issue on whether an edit url should be included on a 
document that one cannot edit.

Looking for a workaround.
http://groups.google.com/group/gdata-dotnet-client-
library/browse_thread/thread/87a438a7c2c57f4c

Original issue reported on code.google.com by goodmans...@gmail.com on 2 Feb 2009 at 7:26

GoogleCodeExporter commented 8 years ago
looking at this. 

Original comment by fman...@gmail.com on 3 Feb 2009 at 10:33

GoogleCodeExporter commented 8 years ago
In general this is a service bug. The interpretation of the edit-link inside an 
entry is so, that, if not present the 
document is read only, if present, the retriever of the entry should be able to 
edit it.

NOW, this still means that your code needs to be prepared that you were removed 
from the access list in 
between the retrieval and the point you execute the edit operation. So it's not 
a guarantee, only a "at this 
point in time you were able to". 

The doclist service has an internal bug filed against this. I will close this 
bug against the .net client (as the .net 
client does the right thing). Feel free to copy this bug into the service 
buglist so that you might get notified 
when the doclist service fixes this. 

Original comment by fman...@gmail.com on 5 Feb 2009 at 10:04