My first stab at a Remoting Article...

Last night I broke down and wrote my first remoting article. .  It really made me appreciate what it takes to be a good writer because I'm not one.  take a subject like remoting for instance.  Where do you really start?  Many people think that breaking stuff into .dlls is 'multi-tiered' and I've met a LOT of folks that think this is the case.  So the pitch for remoting falls upon deaf ears.  Until they actually are confronted with having to move stuff to different machines and run them accordingly, they won't really see that hard coded .dlls won't cut it.  Then the next crowd is the 'web services are easy' so I'll make a web service out of it.  (I'm not in any way implying that Web services are easy or that people that use web services are lazy - far from it).  The problem is that with .NET, it's pretty 'easy' to do a lot of things, but doing things securely, efficiently and that scale well is a whole different issue.  Some folks won't see this until they deploy and have the thing not work well. 

After you get through this hurdle, there's the real part, namely the technical nuances of remoting.  Trying to explain the difference between client activated and server activated objects wthout having someone see them both in action is pretty tough.  I read about them quite a bit and never really got it until I started working through them.  Then there's hosting the things.  Then there's securing the stuff.  So it's pretty hard to write about without doing a lot of background explanation which is what sort of muddles the water for a lot of people. Anyway, I'm thinking that if I do like a 5 part series on it I can probably touch upon a lot of the everyday stuff you come across.  Then again, I'm still fairly new to remoting so I myself have a lot of learning too.