I have added some support for WebDAV-notifications to the client library.
(Not yet completly finished)

Now I have some questions about our server implementation:

1. the POLL method returns some thing like
        <?xml version="1.0" encoding="UTF-8"?>
        <multistatus xmlns="DAV:">
          <response>
            <href>/c</href>
            <status>HTTP/1.1 200 OK</status>
            <N:subscriptionID xmlns:N="http://schemas.microsoft.com/Exchange/";>
              <li>12</li>
              <N:event>
                <N:information name="uri">/c/test.html</N:information>
              </N:event>
            </N:subscriptionID>
          </response>
        </multistatus>
  I found no specification about the event and the information tag.
  It contains information about the resources which are changed.
  That's really usefull information!
  Is there any spec about it?
  It is an extension of an extension, and I'm not sure how to support
  this in the webdav client lib.
  Is it OK to support it by special methods and comment it as extension?

2. what makes the EVENT method

3. Currently Subscriptions are transient. I.e. if the server restarts,
  all subscriptions are lost. So observation of an WebDAV server may be
  incomplete.
  Has anybody thought about makeing subscriptions persitent?
  I think about storing them as resources under a special path
  (configurable, something like /subscriptions). Events catched for the
  subscriptions must be stored too, may be as content of the resource.

Any thoughts?

Thanks, Stefan

--
+--------------------------------------------+
|                                            |
|  Stefan L�tzkendorf                        |
|                                            |
|  Institut f�r Terminologie und             |
|  angewandte Wissensforschung (itaw) GmbH   |
|                                            |
|  Sitz: Georgenstr. 35                      |
|        10117 Berlin                        |
|  Tel.: ++49 (030) 30 86 20 84              |
|  Fax : ++49 (030) 30 86 20 87              |
|                                            |
+--------------------------------------------+


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to