Introduction

It is possible to tune DotMSN to match your connection setup. For example a lot of companies use a proxy to access the internet. Since version 2.0 it is possible to setup your connection properties. All these properties are combined in a single class: ConnectivitySettings. Within this class you can set proxies, webproxies and custom server addresses. When you are using the Messenger and Conversation façade the ConnectivitySettings are simply accessible through the ConnectivitySettings in the Messenger class. These settings will then be used for all connections being created, either by the nameserver processor, or the switchboard processor. However if you are using the logic classes directly, you must ensure that (network) processors (logic classes) must always be handed over an instance of ConnectivitySettings to connect properly. Here is an example of how to setup a proxy:

messenger.ConnectivitySettings.ProxyHost = "10.0.0.100";
messenger.ConnectivitySettings.ProxyPort = 8080;
messenger.ConnectivitySettings.ProxyType = ProxyType.Socks4;
messenger.ConnectivitySettings.WebProxy  = new System.Net.WebProxy("10.0.0.100", 8080);
			

In this example, the company’s internal Proxy server at IP address 10.0.0.100 at port 8080 is used. As you can see it is important that you also set the WebProxy property. This setting is used when a HTTP resource is accessed. In DotMSN this is primarily the Nexus, or passport.com, authentication service. If you do not set this you may not be able to connect to the service.

Custom servers

If you want you can specify your own server by setting the Host and Port properties in the ConnectivitySettings class. Note that is almost never necessary and the default settings will do for most application programmers. You can also change the URI that is used to access the Nexus authentication service. This can be done via the PassportUri property.