[cosmo-dev] Caldav server as calendar proxy

[Andre-John Mas]

On this day "Brian Moseley" wrote:

> On Nov 19, 2007 11:53 AM, Andre-John Mas <ajmas at sympatico.ca> wrote:
> 
> > I am currently in the process of looking at the source code
> > related to the caldav server portion of Cosmo, in the hopes of
> > possibly coming up with a solution that would allow wrapping of
> > other calendar server APIs. The one that I would be most interested
> > in interfacing with is the Google Calendar API.
> 
> that sounds like a very useful project!
> 

Other than simply documenting their Google Calendar API, it
turns out Google also provided a client library for doing the
communciation:

http://code.google.com/p/gdata-java-client/downloads/list

with the JavaDoc being here:

http://code.google.com/apis/gdata/javadoc/

I'll look at documenting how these can map to the Caldav requests.

The way I had originally designed the API I was working on
was to define a 'CalendarService' class that would be
instantiated using and user context and then providing access
based on the context. For example:

  abstract class CalendarService {
    public CalendarService getCalendarService ( User user );
  }

This class would provide all the general functionality for
listing, creating, deleting and other stuff related to calendars.

Another class, called 'Calendar' would provide the name,
description, and other attributes about the calendar. It would also
provide calendar specific operations for creating, editing and
deleting events.

Looking at the Google Calendar API makes me wonder whether this
class would be necessary, since this could be resumed by a 
CalendarContext class and having the CalendarService class perform
these operations.

I haven't much background on Spring, so I will need to aquaint
myself with the API and the philosophy behind it.

Andre