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.
Hmmm. What is the use case you have in mind for persistent subscriptions? I know Daniel had something in mind like clustering, multiple edit clients that are notified of each other changes, etc. I do not think they would need persistent subscriptions.
Anyway, what is your idea?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
