I'm currently working through the Visual Basic version of Ingo Rammer's Remoting book (I dropped my copy of the C# version in a bowl of water. It's a long story....) and I'm noticing that he's strongly warning against using Client Activated Objects with non-default constructors. For the remoting application we're working on, though, those kind of objects are just what we need.
Our application is a multi-machine test framework. Basically, every time a test is run, we re-image both the client (master test machine) and the server (slave test machine). Since we have remote install capabilities in our lab distribution harness it's no problem at all to build an install package that distributes the server application along with the client application on the master test machine.
I guess my point is beware of any absolute hard-and-fast rules. There are always exceptions...
11:35:19 PM 
|
