Oliver Zeigermann wrote:
Stefan L�tzkendorf wrote:
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?
I thougth about an application that observes a webdav server, maybe to index documents, or to keep a workflow system uptodate. If the webdav server application is restarted, for what reasons ever, there will be a time where changes on the webdav server are lost, i.e. the observer is not informed, until it subscribes again. If subscriptions are persitent, the server knows about them afer restart, and no interruption of the observation does occur.
May be it is sufficent to have short subscription lifetimes, and refresh the subscriptions often, so the interuption may be short enought.
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
