activities!

Request:
--------
PROPFIND /svn/repos/$svn/act/the-activity HTTP/1.0
Content-Length: ...

<?xml version="1.0" encoding="utf-8"?>
<D:propfind xmlns:D="DAV:"><D:prop>
  <D:resourcetype/>
</D:prop></D:propfind>
--------

Response:
---------
HTTP/1.1 207 Multi-Status
Date: Mon, 05 Feb 2001 14:36:26 GMT
Server: Apache/2.0b1-dev (Unix) DAV/2 SVN/0.1
Content-Length: 315
Connection: close
Content-Type: text/xml; charset="utf-8"

<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
<D:response xmlns:lp1="DAV:">
<D:href>/svn/repos/$svn/act/the-activity</D:href>
<D:propstat>
<D:prop>
<lp1:resourcetype><D:activity/></lp1:resourcetype>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
---------

Note the <D:activity/> element in there. hehe...

Basically, the neat part about this is that we have a completely synthesized
resource on the server (the activity). It is alive and kicking.

It meets our needs at this point, but it doesn't actually have the standard
activity properties defined on it yet. (not until later on) The nice thing
is that this also indicates our activity mapping database is working and
that we can look them up and do a CHECKOUT into that activity (which is the
next step).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/