Hi,

Thank you for your patience, we have confirmed that <batch:interrupted> is
only inserted at the entry level.  The confusing bit from the documentation
is an error, we are going to fix that.  Thanks!

Austin

On Wed, Jun 11, 2008 at 10:03 AM, Matt Pruden <[EMAIL PROTECTED]> wrote:

>
> In working on the batch processing in Google Calendar, I noticed this
> in the docs at: http://code.google.com/apis/gdata/batch.html
>
> "The <batch:interrupted> element is inserted only on the feed level,
> never on the entry level. ... This element can only appear in the last
> entry of the feed returned in the body of the response"
>
> To me, this means that the <batch:interrupted> element is only on the
> feed and only in the last entry.  How can this be?
>
> Here's an example response returned from a batch URI request.  Notice
> that the <batch:interrupted> element exists in the last entry, not the
> feed.  (unnecessary elements removed)
>
> <atom:feed>
>    <atom:title type="text">
>        Batch Feed
>    </atom:title>
>    <atom:entry>
>        <atom:title type="text">
>            MOTHERS DAY ON SUNDAY
>        </atom:title>
>        <batch:id>
>            0
>        </batch:id>
>        <batch:status code="201" reason="Created"/>
>        <batch:operation type="insert"/>
>    </atom:entry>
>    <atom:entry>
>        <atom:title type="text">
>            Fatal Error
>        </atom:title>
>        <atom:content type="text">
>            Feed processing was interrupted.
>        </atom:content>
>        <batch:interrupted reason="[Line 8, Column 6371, element
> ns0:email] Email must have a value." parsed="8" success="8" error="0"
> unprocessed="0"/>
>    </atom:entry>
> </atom:feed>
>
> Whatever the case, it seems even Google's Python client API expects
> the batch:interrupted element to be on the feed, not on the entry.
> For example:
>
> >>> entry = gdata.BatchEntry()
> >>> feed = gdata.BatchFeed()
> >>> 'interrupted' in dir(entry)
> False
> >>> 'interrupted' in dir(feed)
> True
> >>>
>
> Is this a bug?  If so is it with the docs and/or with the
> implementation of the Python gdata library?
>
> If anyone else is running into this, you can always use the
> ingeniously developed fallback, the extension_elements for the entry.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to