You're making a remote method call to a network service. Any time you do
such a thing, your app has a dependency upon something it has no control
over, and which is dependent upon a variety of circumstances over which your
app has no control. Therefore, you cannot expect it to always succeeed.
There are so many things that can go wrong with an Internet messaging
connection that it is amazing that the Internet works at all. Part of the
reason is that there are safeguards built into networked systems, such as
redundancy, round-robin, and Cyclic Redundancy Checks, and so on.

Signature
HTH,
Kevin Spencer
Microsoft MVP
Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net
> Alright Googler Groupers!
>
[quoted text clipped - 42 lines]
> HttpRequestHandler http = new HttpRequestHandler(connectionURL);
> string response = http.POST(stuffToPost);
Brenton Unger - MCSD.NET - 30 Apr 2007 20:12 GMT
Kevin,
All of what you said is well understood and I've got all my bases
covered in the event that I'm not able to communicate with the other
machines. Thanks for the input, though.
The problem here is not that I'm not able to communicate with the
remote machines; but rather that I'm communicating fine I'm just not
able to tell the framwork to accept the certificate! Obviously the
framework itself is having a problem accepting a certificate
regardless of the fact that I'm telling it in every way I know how to
direct the framework to do so to accept it.
Does anyone else have any input that can help out?
TIA
~Brenton
> You're making a remote method call to a network service. Any time you do
> such a thing, your app has a dependency upon something it has no control
[quoted text clipped - 63 lines]
>
> - Show quoted text -