On Mar 27, 7:17 am, Joe Webb 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.
Thanks, I actually thought of that, but I was hoping to devise another
way so that the client doesn't need to do anything other than update
the data. Part of my reason for doing this is to make the save on the
client quicker; the NS API is currently slowing things down because
its promoting my transaction to DTC. A web service may be quicker,
but there's a chance that the update call will fail for some reason
(we sometimes have network hiccups). If that happens, the save will
succeed, but the subscription won't be added.
My other reason is that I currently have two different places in the
application where I need to add a subscriber. Moving forward, there
may be more. While I've re-factored the code, I still have to
remember to include the call (which I almost forgot, actually).
Andy >> Stay informed about: NS adding its own subscribers?