tealie mcdearson's Bookmarks tagged !science →  View Popular

The ClientLogin method requires having access to the username and password for a Google Account. To receive an authentication token using the ClientLogin mechanism, send a POST request to the following URL:

https://www.google.com/accounts/ClientLogin

The POST body should contain a set of query parameters, as described in the following table. They should look like parameters passed by an HTML form, using the application/x-www-form-urlencoded content type.

If it succeeds, then the response from the service is an HTTP 200 OK status code, plus three long alphanumeric codes in the body of the response: SID, LSID, and Auth. The Auth value is the authorization token that you'll send to Calendar with your request, so keep a copy of that value. You can ignore the SID and LSID values.

Since all requests to private feeds require authentication, you have to set the Authorization header in the request, using the following format:

Authorization: GoogleLogin auth=yourAuthToken

Where yourAuthToken is the Auth string returned by the login request.

Creating single-occurrence events

Adding an event to a calendar is a little bit more complicated than getting a feed, because you need to create the XML code or client-library object representing the event, and you need to use authentication.

First, create an entry of the Event kind. (For more information about kinds, see the Kinds document.) For example, you might create the following entry:

<entry xmlns='http://www.w3.org/2005/Atom'
    xmlns:gd='http://schemas.google.com/g/2005'>
  <category scheme='http://schemas.google.com/g/2005#kind'
    term='http://schemas.google.com/g/2005#event'></category>
  <title type='text'>Tennis with Beth</title>
  <content type='text'>Meet for a quick lesson.</content>
  <gd:transparency
    value='http://schemas.google.com/g/2005#event.opaque'>
  </gd:transparency>
  <gd:eventStatus
    value='http://schemas.google.com/g/2005#event.confirmed'>
  </gd:eventStatus>
  <gd:where valueString='Rolling Lawn Courts'></gd:where>
  <gd:when startTime='2006-04-17T15:00:00.000Z'
    endTime='2006-04-17T17:00:00.000Z'></gd:when>
</entry>

Note that this entry does not contain the standard APP <author> tag. The server will insert author information based on the user that submits the request (i.e. the user whose authentication token accompanies the request).

To post an entry, send the following HTTP request to Calendar, using a special "default" URL (and an Authorization header; see the section on authentication above). Calendar automatically redirects the default URL to the URL of the read/write private feed of the calendar belonging to the authenticated user. (Note that you don't have to use the default URL to send a POST request to Calendar; you can specify the user ID instead of "default" if you prefer. For more information, see the Calendar feed types reference.)

The content that you send with the POST request should be the <entry> element you created above, using the application/atom+xml content type.

Just like in the previous example, Calendar may return an HTTP 302 redirect; if so, then the redirect URL has a new parameter, gsessionid, appended to it. If you received the redirect, then send the same POST request again, with the same Authorization header and the same content, but with the gsessionid parameter appended. The response may also include a S cookie, which you should store and send this cookie with future requests as appropriate. Please see the knowledge base for more information on handling sessions with the Calendar data API. Please note: if a session ID indicated in a cookie header conflicts with the session ID passed as a gsessionid URL parameter, you will get caught in a redirect loop.

To create an event using Google Calendar's quick add feature, set the event entry's content to the quick add string you'd like to use. Then add a <gCal:quickadd> element with a value attribute set to true. For example, the following event <entry> element will create an event on April 11 from 3pm-3:30pm with a title of 'Tennis with John':

<entry xmlns='http://www.w3.org/2005/Atom' xmlns:gCal='http://schemas.google.com/gCal/2005'>
  <content type="html">Tennis with John April 11 3pm-3:30pm</content>
  <gCal:quickadd value="true"/>
</entry>

The response from the server will contain an event <entry> with the appropriate fields populated by the server. Note that the <content> element is now empty and the <gCal:quickadd> element is no longer present:

<entry xmlns="http://www.w3.org/2005/Atom" xmlns:gd="http://schemas.google.com/g/2005">
  ...
  <title type="text">Tennis with John</title>
  <content type="text" />
  <gd:when endTime="2007-04-11T15:30:00.000-07:00" startTime="2007-04-11T15:00:00.000-07:00" />
  ...
</entry>

What Is REST?

What is REST anyway? It is an architectural style.
An architectural style is a named, coordinated set of
architectural constraints.

A MIDlet can access all the attributes defined inside both the
manifest file (which is part of a JAR) and those inside the JAD
file. The complete package name to the method that will return
information about the properties is

javax.microedition.midlet.MIDlet.getAppProperty(String name)