After this discussion, I figured it would be best to list the 'bugs' that we
found in this thread, so we can properly report them:

1- Modification/addition of acl entries through the apis SOMETIMES results
in 'false' positives (that is, no error being reported by Google, but task
was an actual failure). Two different cases were discussed in this thread:
a) cases reported by David at the beginning of this thread AND b)
'non-existent account used in acl' case, reported by myself.

2- Modification/addition of acl entries through the apis SOMETIMES 'gets out
of synch' with the Google Docs GUI (reported by me). More specifically, the
GUI does not reflect all the programmatic additions/modifications even after
a delay.

I think that they deserve to be reported separately, and we may even think
of reporting 1.a and 1.b separately (especially given that David knows the
details of 1.a, and I know the details of 1.b :-)).

Does this breakup make sense?
-Patricia

> -----Original Message-----
> From: Google-Docs-Data-APIs@googlegroups.com 
> [mailto:google-docs-data-a...@googlegroups.com] On Behalf Of 
> Patricia Goldweic
> Sent: Wednesday, June 24, 2009 2:15 PM
> To: Google-Docs-Data-APIs@googlegroups.com
> Subject: [Google-Docs-Data-APIs] Re: The response from 
> modifying the ACL is returning false-positives
> 
> 
> Interesting, that's also the way I was planning to use this 
> :-), since my app automatically provisions accounts. So the 
> acls were being added before the accounts got created, and 
> that's how I discovered the buggy behavior. I ended up 
> resorting to a work around that avoids adding acls for 
> non-existing accounts; they only get added now when the 
> accounts end up being provisioned. 
> 
> -Patricia
> 
> > -----Original Message-----
> > From: Google-Docs-Data-APIs@googlegroups.com
> > [mailto:google-docs-data-a...@googlegroups.com] On Behalf Of Daniel 
> > Marashlian
> > Sent: Wednesday, June 24, 2009 1:14 PM
> > To: Google Docs Data APIs
> > Subject: [Google-Docs-Data-APIs] Re: The response from 
> modifying the 
> > ACL is returning false-positives
> > 
> > 
> > At least with the way that I'm using it... (unless the 
> email is in a 
> > bad format) I think Google shouldn't limit the ACL's 
> getting inserted 
> > in.
> > 
> > For instance... I want to hire "Bob" next week, so I go 
> into my Google 
> > Docs account and enter b...@mycompany.com into all of my GDocs (from 
> > the UI). But b...@mycompany.com is not a Google account yet. 
> So I hire 
> > Bob next week, and tell him that his email is 
> b...@mycompany.com and he 
> > should go to google docs and create an account under that 
> name, cause 
> > he's already added to all of the company documentation.
> > 
> > It seems like this is possible now, though it's spotty. 
> We're adding 
> > in potential Google Docs accounts from the API because at 
> first we're 
> > using the people's email addresses that I have in my database (at a 
> > later point, they have the option to change it to a preferred Google
> > Email) then if that user wants to interact with the google 
> doc that is 
> > organized in my system, they would click on the link for 
> the file, and 
> > it would push them to the document.
> > 
> > now, if you don't have a google docs account with 
> b...@mycompany.com, 
> > that's where Google Docs Shines! They just prompt you to create an 
> > account with that email. It doesn't matter if it's a gmail 
> account or 
> > not.
> > 
> > This is how I would like it to work... in my testing it 
> does, but not 
> > 100% of the time...
> > 
> > On Jun 24, 10:55 am, "Patricia Goldweic" 
> <pgoldw...@northwestern.edu>
> > wrote:
> > > Hi Eric,
> > > I agree with your statement. However, if these acls get
> > added for any
> > > reason (e.g. a program that is not verifying that they
> > correspond to
> > > valid users), and they show up in the Docs GUI, you would
> > expect them
> > > to work. I think I'd much rather get a failure message 
> from Google 
> > > whenever one tries to add them, so that they wouldn't be
> > propagated to the GUI in the first place.
> > > Would you rather not see this posted as a bug then?
> > > -Patricia
> > >
> > > Patricia Goldweic
> > > pgoldw...@northwestern.edu
> > >
> > > > -----Original Message-----
> > > > From: Google-Docs-Data-APIs@googlegroups.com
> > > > [mailto:google-docs-data-a...@googlegroups.com] On 
> Behalf Of Eric
> > > > (Google)
> > > > Sent: Wednesday, June 24, 2009 12:41 PM
> > > > To: Google Docs Data APIs
> > > > Subject: [Google-Docs-Data-APIs] Re: The response from
> > modifying the
> > > > ACL is returning false-positives
> > >
> > > > Well, you should only be adding
> > > > ACLs that correspond to gDocs users.
> > > > A combination of anything else may appear to work, but 
> I wouldn't 
> > > > trust it.
> > >
> > > > Eric
> > >
> > > > On Jun 24, 10:02 am, Daniel Marashlian
> > <daniel...@gmail.com> wrote:
> > > > > please go ahead :)
> > >
> > > > > I haven't done too much testing after the fact. I'm going
> > > > to do some
> > > > > testing on that scenario you just described.
> > >
> > > > > On Jun 24, 7:33 am, "Patricia Goldweic" 
> > > > > <pgoldw...@northwestern.edu>
> > > > > wrote:
> > >
> > > > > > I've seen this behavior too. In fact, I concluded that,
> > > > if you add
> > > > > > (through the api) an acl entry for a (not yet)existent
> > > > account, you
> > > > > > get no errors at the time you are doing this. 
> However, if the 
> > > > > > account gets later created, those acls which should have
> > > > been placed
> > > > > > in the feed in the previous step, are really not
> > working. This
> > > > > > is consistent with the behavior you just described
> > David, mainly
> > > > > > the fact that non-existent account acls ACTUALLY DO 
> FAIL when
> > > > they are
> > > > > > added (and therefore are not really being added), but
> > > > this is not being reported by Google.
> > > > > > I think this definitely deserves a bug report. Are you
> > > > going to file
> > > > > > this one David, or should I do it?
> > >
> > > > > > Patricia Goldweic
> > > > > > pgoldw...@northwestern.edu
> > >
> > > > > > > -----Original Message-----
> > > > > > > From: Google-Docs-Data-APIs@googlegroups.com
> > > > > > > [mailto:google-docs-data-a...@googlegroups.com] On
> > Behalf Of
> > > > > > > Daniel Marashlian
> > > > > > > Sent: Tuesday, June 23, 2009 5:42 PM
> > > > > > > To: Google Docs Data APIs
> > > > > > > Subject: [Google-Docs-Data-APIs] Re: The response from
> > > > modifying
> > > > > > > the ACL is returning false-positives
> > >
> > > > > > > to make it even more confusing, I've been testing
> > "bad emails"
> > > > > > > like kjhasdf...@pelotonics.com and they show up on the
> > > > UI but not
> > > > > > > in the ACL list... hmmm.
> > >
> > > > > > > Fun times :)
> > >
> > > > > > > On Jun 23, 3:31 pm, Eric Bidelman
> > <api.e...@google.com> wrote:
> > > > > > > > Well, Patricia said these show up in the feed but not
> > > > the Docs
> > > > > > > > UI. You're saying they show up in neither.  I'm 
> a little 
> > > > > > > > confused that there's different behavior across 
> the board.
> > >
> > > > > > > > Eric
> > >
> > > > > > > > On Tue, Jun 23, 2009 at 1:45 PM, Daniel Marashlian
> > > > > > > <daniel...@gmail.com>wrote:
> > >
> > > > > > > > > Wait... I'm confused :)
> > >
> > > > > > > > > So I try to add a user's email to a document, at
> > > > least when I
> > > > > > > > > use the batch processing, it reports back a 
> success but 
> > > > > > > > > when
> > > > > > > I do a GET
> > > > > > > > > on
> > >
> > > > 
> > "http://docs.google.com/feeds/acl/private/full/[docType]%3A[docID]";
> > > > > > > > > and check through the XML for the gAcl:scope that
> > > > user's Email
> > > > > > > > > is not in the list.
> > >
> > > > > > > > > How is that consistently working?
> > >
> > > > > > > > > maybe I'm confused on the separation between 
> the ACL and
> > > > > > > Google Docs.
> > >
> > > > > > > > > On Jun 23, 1:27 pm, Eric Bidelman
> > > > <api.e...@google.com> wrote:
> > > > > > > > > > Thanks for the quick info folks.
> > > > > > > > > > It sounds like the adding ACLs through the API
> > > > > > > consistently works
> > > > > > > > > > (e.g. the correct results show up when
> > querying the ACL
> > > > > > > feed), but
> > > > > > > > > > they're not propagated to Google Docs.  Can 
> one of you
> > > > > > > open a bug
> > > > > > > > > > for this with the detailed info in this thread.
> > >
> > > > > > > > > > Thanks!
> > >
> > > > > > > > > > Eric
> > >
> > > > > > > > > > On Tue, Jun 23, 2009 at 1:09 PM, Daniel Marashlian 
> > > > > > > > > ><daniel...@gmail.com
> > > > > > > > > >wrote:
> > >
> > > > > > > > > > > Hi Eric,
> > >
> > > > > > > > > > > The "single" feed seems to be working more
> > > > consistently,
> > > > > > > > > > > but when it fails it doesn't tell me anything
> > > > in the response.
> > >
> > > > > > > > > > > this is the XML I'm using (maybe I'm doing
> > it wrong):
> > >
> > > > > > > > > > > POST'ing it to: "
> > > > > > > > >http://docs.google.com/feeds/acl/private/full/document
> > > > > > > > > > > %3Adg7wvvh9_51fjcscsvz"
> > >
> > > > > > > > > > > XML:
> > > > > > > > > > > "<entry
> > > > > > > > > > > 
> > xmlns='http://www.w3.org/2005/Atom'xmlns:gAcl='http://
> > > > > > > > > > > schemas.google.com/acl/2007'> <category
> > >
> > > > scheme='http://schemas.google.com/g/2005#kind'term='http:/
> > > > > > > > > > > / schemas.google.com/acl/2007#accessRule'/>
> > > > > > > > > > > <gAcl:role value='writer'/> <gAcl:scope 
> type='user'
> > > > > > > > > > > value='tmal...@pelotonics.com'/> </entry>"
> > >
> > > > > > > > > > > Here is a response from a call that failed:
> > >
> > > > > > > > > > > <?xml version='1.0' encoding='UTF-8'?><entry 
> > > > > > > > > > > xmlns='http://www.w3.org/2005/Atom'
> > > > > > > xmlns:gAcl='http://schemas.google.com/acl/2007'
> > >
> > > > > > > 
> > xmlns:batch='http://schemas.google.com/gdata/batch'><id>http:/
> > > > > > > /
> > >
> > > > > > > 
> > docs.google.com/feeds/acl/private/full/document%3Adg7wvvh9_51f
> > > > > > > jc
> > > > > > > > > > > scsvz/
> > > > > > > > > > > user%3Atmalone%40pelotonics.com
> > > > > > > > > </id><updated>2009-06-23T19:56:20.103Z</
> > > > > > > > > > > updated><category
> > > > > > > scheme='http://schemas.google.com/g/2005#kind'
> > >
> > > > term='http://schemas.google.com/acl/2007#accessRule'/><tit
> > > > > > > > > > > le type='text'>Document Permission - 
> > > > > > > > > > > tmal...@pelotonics.com</title><link
> > > > > > > > > > > rel='self' type='application/atom+xml'
> > > > > > > > > > > href='http://docs.google.com/
> > >
> > > > > > > 
> > feeds/acl/private/full/document%3Adg7wvvh9_51fjcscsvz/user%3At
> > > > > > > ma
> > > > > > > > > > > lone %40pelotonics.com'/><link rel='edit'
> > > > > > > > > > > type='application/atom+xml'
> > >
> > > > href='http://docs.google.com/feeds/acl/private/full/docume
> > > > > > > > > > > nt
> > >
> > > > > > > 
> > %3Adg7wvvh9_51fjcscsvz/user%3Atmalone%40pelotonics.com'/><gAcl
> > > > > > > :r
> > > > > > > > > > > ole value='writer'/><gAcl:scope type='user'
> > > > > > > > > > > value='tmal...@pelotonics.com
> > > > > > > > > '/
> > > > > > > > > > > ></entry>
> > >
> > > > > > > > > > > On Jun 23, 11:07 am, "Patricia Goldweic"
> > > > > > > > > > > <pgoldw...@northwestern.edu>
> > > > > > > > > > > wrote:
> > > > > > > > > > > > Hi Eric,
> > > > > > > > > > > > The response to your question: 'Just so 
> I'm clear,
> > > > > > > these ACLs
> > > > > > > > > > > > never
> > > > > > > > > show
> > > > > > > > > > > up,
> > > > > > > > > > > > correct?' is YES. Those entries DO NOT 
> show up in 
> > > > > > > > > > > > the GUI (even after
> > > > > > > > > a
> > > > > > > > > > > > delay), but they're definitely in the feed.
> > >
> > > > > > > > > > > > I'm not sure who you asking the second
> > question to:
> > > > > > > > > > > > 'also, does the
> > > > > > > > > user
> > > > > > > > > > > > show up when re-querying the doc's ACL 
> feed?  (in
> > > > > > > my case, I
> > > > > > > > > > > > can see
> > > > > > > > > the
> > > > > > > > > > > ACL
> > > > > > > > > > > > entries through the api if I re-query).
> > >
> > > > > > > > > > > > -Patricia
> > >
> > > > > > > > > > > >   _____
> > >
> > > > > > > > > > > > From: Google-Docs-Data-APIs@googlegroups.com
> > > > > > > > > > > > 
> [mailto:google-docs-data-a...@googlegroups.com] On
> > > > > > > Behalf Of
> > > > > > > > > > > > Eric
> > > > > > > > > > > Bidelman
> > > > > > > > > > > > Sent: Tuesday, June 23, 2009 12:45 PM
> > > > > > > > > > > > To: Google-Docs-Data-APIs@googlegroups.com
> > > > > > > > > > > > Subject: [Google-Docs-Data-APIs] Re: The
> > > > response from
> > > > > > > > > > > > modifying the
> > > > > > > > > ACL
> > > > > > > > > > > is
> > > > > > > > > > > > returning false-positives
> > >
> > > > > > > > > > > > Hi all,
> > >
> > > > > > > > > > > > Please report bugs if you think they are. 
> >  I triage
> > > > > > > the issue
> > > > > > > > > > > > tracker on a regular basis.  It's also 
> helpful to
> > > > > > > post in the
> > > > > > > > > > > > forum (as
> > > > > > > > > you've
> > > > > > > > > > > done
> > > > > > > > > > > > :))
> > > > > > > > > > > > so others can follow any issues.
> > >
> > > > > > > > > > > > Sometimes there are small delays between
> > > > doing something
> > > > > > > > > > > > in the API
> > > > > > > > > and
> > > > > > > > > > > > when it actually shows up in a re-query
> > or the Docs
> > > > > > > UI. Just
> > > > > > > > > > > > so I'm
> > > > > > > > > > > clear,
> > > > > > > > > > > > these ACLs never show up, correct?
> > >
> > > > > > > > > > > > Daniel, do you see the same happening when NOT
> > > > > > > using a batch feed?
> > > > > > > > > > > > Inserting a entry and inserting a single
> > > > entry inside of
> > > > > > > > > > > > a batch feed go through different pipelines.
> > >
> > > > > > > > > > > > Also, does the user show up when re-querying the
> > > > > > > doc's ACL feed?
> > >
> > > > > > > > > > > > Eric
> > >
> > > > > > > > > > > > On Tue, Jun 23, 2009 at 8:01 AM, 
> Patricia Goldweic
> > >
> > > > > > > > > > > > <pgoldw...@northwestern.edu> wrote:
> > >
> > > > > > > > > > > > I've also noticed problems with using 
> the apis to
> > > > > > > modify/add
> > > > > > > > > > > > acl
> > > > > > > > > entries.
> > > > > > > > > > > In
> > > > > > > > > > > > my case, some entries get added, but 
> then, they DO
> > > > > > > NOT display
> > > > > > > > > > > > on the
> > > > > > > > > GUI
> > > > > > > > > > > > (as if the document was not being shared
> > with those
> > > > > > > > > > > > people, even
> > > > > > > > > though
> > > > > > > > > > > the
> > > > > > > > > > > > acl entries are actually there, and sharing
> > > > > > > actually works).
> > > > > > > > > > > > This
> > > > > > > > > only
> > > > > > > > > > > > happens once in
> > >
> > > ...
> > >
> > > read more »
> > > 
> 
> 
> 
> > 



--~--~---------~--~----~------------~-------~--~----~
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