On Mar 26, 1:32 pm, "Andy" <a...@med-associates.com> wrote:
> Hi,
>
> My database has a flag that indicates if our customers would like to
> receive notifications. Currently, our sales staff manages
> subscriptions on behalf of our customers. The settings for all
> customers is the same, so its only a matter of enabling or disabling a
> subscription (or creating if it doesn't exist).
>
> Currently, my application uses the NS API to update subscriber and
> subscription information behind the scenes. The problem is that I
> must deploy the NS client API to all users of my application and
> register the instance on each workstation.
>
> I was thinking that I could use NS to automatically update these
> settings, maybe once a day by tracking the flag as it changes.
>
> My question is, would this be a viable way to go, or am I twisting the
> purpose of NS too much?
>
> Thanks
> Andy

On Mon, 26 Mar 2007 10:35:41 -0700, Andy wrote:

> On Mar 26, 1:32 pm, "Andy" <a...@med-associates.com> wrote:
>> Hi,
>>
>> My database has a flag that indicates if our customers would like to
>> receive notifications. Currently, our sales staff manages
>> subscriptions on behalf of our customers. The settings for all
>> customers is the same, so its only a matter of enabling or disabling a
>> subscription (or creating if it doesn't exist).
>>
>> Currently, my application uses the NS API to update subscriber and
>> subscription information behind the scenes. The problem is that I
>> must deploy the NS client API to all users of my application and
>> register the instance on each workstation.
>>
>> I was thinking that I could use NS to automatically update these
>> settings, maybe once a day by tracking the flag as it changes.
>>
>> My question is, would this be a viable way to go, or am I twisting the
>> purpose of NS too much?
>>
>> Thanks
>> Andy
>
> I should also add that I will need NS to send an email regarding
> changes as well to another employee here.

On Mar 27, 7:17 am, Joe Webb <j...@webbtechsolutions.com> wrote:
> You could create a web service wrapper for the NS API. Have the web
> service run on the server that NS runs on. The clients could employ the
> web service to manage the subscriptions. So, you wouldn't need to install
> the NS client API on each workstation.
>
> You could probably also create the web service so that it also manages the
> other settings you've mentioned.