Michael Oliver wrote:
I am starting work on a persistent mechanism for storing the subscriptions in xml in a particular path.
Fine!
Then I will be creating (already started) a secondary store to plug into our primary XML store to match subscriptions to the uri of the content store methods and use those matches to generate am email queue from the subscriptions, in another path. Then we have a cron admin daemon that will scan that path and pick up and send the messages.
Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036
-----Original Message-----
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 4:25 AM
To: Slide Developers Mailing List
Subject: Re: WebDAV and Notifications
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?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
