Welcome to MSDN Blogs Sign in | Join | Help

September 2004 - Posts

v1.0 sp3 of the framework now has typefilterlevel set to Low by default, similar to the setting in v1.1 version of the framework. This means the server will not deserialize ObjRef's, Leases and other such objects by default. The way to fix is exactly Read More...
The Soap Formatter is on the path of deprecation. Starting in v2.0 of the framework the usefulness of the soap formatter would be highly limited since it will not support some of the new v2.0 framework features such as generics and the version tolerant Read More...
v2.0 for the .net framework adds IPv6 support to .net remoting. In v2.0 you can use the bindTo property on channels to bind your server channel to IPv6 addresses. To enable this functionality you need to turn on ipv6 support in machine.config for system.net. Read More...
Remoting implements a lease based lifetime management. There is no reference counting since doing so for remote objects is not trivial and for cases where networks can be faulty its bound to cause more issues. Thus clients need to make sure they keep Read More...
As is common knowledge there are two types of remoting objects, server-activated objects (aka wellknown) and client activated objects. The client side proxies for these objects have different behaviour as well. Some issues to be aware of are: 1. RemotingServices.Connect Read More...
Reflection should work just fine over remoting proxies. In some cases you need to be a little careful since for some cases the entire type heirarchy isnt available mainly for wellknown proxies, since the proxy is generated without a remote invocation, Read More...
There are a couple of ways you can secure remoting endpoints: 1. Host in IIS: hosting your server components in IIS allows you to secure your application using IIS' inbuilt authentication (basic/digest/ntlm/kerb) and encryption (using https) mechanisms. Read More...
Binary and Soap formatters have a way to specify a SerializationBinder. Each time a type is being deserialized the BindToType method on the registered binder will be invoked. This gives the user the opportunity to load his/her own custom type instead Read More...
This is a very common question. Whether there is affinity between remoting objects and registered channels. The answer is no. Any channel registered in the appdomain hosting a remoting object can dispatch to it. Thus if you have a "secure" channel and Read More...
There are two types of remotable objects, wellknown and client activated. The server controls which version of the type its publishing (either using registerwellknownservertype or using RemotingServices.Marshal). Whereas for client-activated objects the Read More...
As I had described in my previous post its possible to change client side sink properties for remoting proxies. For client-activated objects it can be a little tricky since you dont get a proxy till a constructor is invoked remotely( and this might be Read More...
 
Page view tracker