Partial Response and Partial Update added to Google APIs

In order to make APIs faster, Google introduced two experimental features in Google Data Protocol, partial response and partial update. “Say, you’re writing a Android calendar widget, and you want to display time & title of recently changed events on Google Calendar. With old Calendar Data API, you would request calendar’s events feed and receive […]

In order to make APIs faster, Google introduced two experimental features in Google Data Protocol, partial response and partial update. “Say, you’re writing a Android calendar widget, and you want to display time & title of recently changed events on Google Calendar. With old Calendar Data API, you would request calendar’s events feed and receive a large amount of information in response. And with partial response you can use ‘fields query’ parameter to request relevant information, for .e.g.: GET http://www.google.com/calendar/feeds/zachpm@google.com/private/full?fields=entry(title,gd:when). But say you want to also enable widget to change time of calendar events. With partial update, you can easily accomplish this: simply edit the data you received in partial response and use HTTP PATCH verb to send modified data back to the server.

More info: Making APIs Faster: Introducing Partial Response and Partial Update