microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: digest notifications for different events

Subject: Re: digest notifications for different events
From: Joe Webb
Date: Wed, 08 Mar 2006 13:47:56 -0600
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Gotcha - 

Here's a thread that may help with passing optional parameters.

http://groups.google.com/group/microsoft.public.sqlserver.notificationsvcs/browse_thread/thread/1937323c4b8361fd/92bb28d6a17e2139?q=optional+&rnum=2#92bb28d6a17e2139
Joe



-- 
Joe Webb
SQL Server MVP
http://www.sqlns.com


~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)


On 3 Mar 2006 03:58:42 -0800, "gotcha" <[email protected]> wrote:

>I also came up with that idea.
>
>There are some events which I should be able to merge into one event
>class, with an extra parameter.
>This would work quite well for events like "document added" and
>"document changed", because their event classes are almost the same,
>and users subscribe to these events in the same way.
>
>However, some other document-related events are less suitable for
>merging.
>These events have other event fields and other subscription parameters.
>
>For example, users can receive a notification when the end of the
>publication term for a document approaches.
>In their subscription, they're able to set the number of days before
>the end date they want to be warned.
>
>Merging all event classes would be possible, but it would leave me with
>complicated event classes and lots of subscription parameters.
>In addition to that, users should still be able to subscribe to some of
>the merged events, and not all.
>This would result in another subscription parameter, which should hold
>all the events the user subscribed to.
>
>If there is no better solution, I'll try to work something out with
>merged event classes, but I was hoping there was a better
>alternative...

<Prev in Thread] Current Thread [Next in Thread>