Plan

This is my plan for implementing Tickets in CalDav4j using the http://www.sharemation.com/~milele/public/dav/draft-ito-dav-ticket-00.txt spec.

As of now there is no Ticket Support in Scooby, but there is in Cosmo. Please See CosmoTickets.

I will need to implement:

• The Following HTTPMethods:
  • MKTICKET
  • DELTICKET

Furthermore I will need to handle (I will barely be extending it):

• The HTTPMethod:
  • PROPFIND
    • I will do this by implementing a TicketDiscoveryProperty Object

High Level Design

1. TicketRequest
   • This is a class that will hold all the information related to a ticket request.
   • Will have the following heirarchy:
     • OutputsDOMBase -> TicketRequest
2. TicketResponse
   • This is a class that will hold all information related to a valid instantiated ticket.
3. MkTicketMethod
   • Is a class that will use TicketRequest object to make an HTTP Request and process the response using a TicketResponse Object.
   • Will use the following Heirarchy:
     • XMLResponseMethod -> MkTicketMethod
4. DelTicketMethod
   • Will generate a request to delete a ticket and handle the response
   • Will use the following Heirarchy:
     • HTTPMethodBase -> DelTicketMethod
   • Has no Request or Return Bodies
5. TicketDiscoveryProperty
   • This Object will handle the reponse of a Propfind method.
   • Will have the following heirarchy:
     • OutputsDOMBase -> TicketDiscovery;

Deviantions From Spec

In order to comply with Cosmo the following deviations are planned:

• The Custom XML namespace http://www.xythos.com/namespaces/StorageServer/ is used for XML elements defined by the spec (ticketdiscovery, ticketinfo, id, timeout and visits)

• The Error response 403 has been added to the DELTICKET request in order to show that the user is not the owner and can therefore not delete the ticket.

• The root user along with the owner are the only users that can delete the ticket

-- EdBindl - 07 Jun 2006