Mike,
>>1) Having confidence that the service providor will be in business next year
>>2) The providor being able to handle the bandwidth
>>3) Some security issues
>
>Doug, typically, if you are to rely on someone elses web service, yeah, these are things you need to consider. But in response to Jim's "Server" component, he would be the Service Provider. The web service could run on his Internet server, or Intranet server, or on any machine with IIS anywhere on his LAN. Security and bandwith are up to him.
Right.
For example, we're thining of using web services to validate addresses and so forth. If the service goes down or disappears then we can control how to best respond. For
our web services we will take responsibility for having them online at all times. This way we do not expose our clients to 3rd party vaguries.
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
