Performance was somewhat of an issue. It's acceptable, but not great. But
we're only talking about the Subscription Management Application side
of things, not the SSNS part. In these apps, subscriptions are not managed
that often, so it's not too much of an issue. Of course it will somewhat
depend on the bandwidth you have going to the SSNS server, it's load, etc.
They were hosted on different providers.
You can implement web services security as needed. For example, you can
encrypt the payload, implement uid and pwd encrypted in SOAP headers,
restrict IP addresses, etc.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Sun, 24 Dec 2006 09:36:37 +0000, TonyS wrote:
> Hi Joe,
> Can you comment on what sort of performance (or lack of) did you get with
> this architecture?
> Also were the two systems hosted on the same or across different providers
> or was one hosted and you hosted the other?
> What sort of security did you implement for the web service?
> Was there any issue in getting the isp to host your xml web service
> (assuming that you used an isp for this)
> Thanks a lot in advance
> Tony S.
> "Joe Webb" <[email protected]> wrote in message
> news:[email protected]
>>I don't of a hosting company that supports SSNS. What I've done in the
>> past is to create the subscription management interface on the hosted
>> site and then use XML web services to communicate to another server
>> that hosts the SSNS app.
>> Joe Webb
>> SQL Server MVP
>> Get up to speed quickly with SQLNS
>> I support PASS, the Professional Association for SQL Server.
>> (www.sqlpass.org)On Thu, 8 Jun 2006 16:02:01 -0700, deejjaayy
>> <[email protected]> wrote:
>>>Apologies if this is considered off-topic, however does anyone know of any
>>>hosting companies that provide good quality service as well as the
>>>MS SQL Server 2005 (with Notification Services)
>>>.NET Framework v2.0
>>>Support for MSMQ
>>>Thanks in advance...