Hi Stefan, nice to see that you are dealing with events... See my comments below
Stefan L�tzkendorf schrieb:
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?
I've introduced this event information tag to enable events to add specific data to the occured event.
To add this information to an event just implement the RemoteInformation interface. Have a look at the ResourceEvent class to understand how it works. It's really simple.
As it is Slide specific and event specific there is no spec about it. I'm not sure if we should use this (nice) feature as Exchange does not provide this kind of information. If an application using notifications should work with Slide and Exchange it will not work anymore if the application relies on this additional information. So I've dropped this approach for the Projector framework.
2. what makes the EVENT method
The EVENT methods can be used to fire a custom event. This might be useful if you are having a clustered client side application and you want to use Slide to distribute some events to all listeners. I don't know if this is really useful. What do you think?
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?
This might be a solution but might slow down Slide. Any work in this area is very welcome!
Regards,
Daniel
Thanks, Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
