Remoting?

how to start to program with remoting in vb.net

William — Wed, 23 Nov 2005 10:05:00 GMT

hi i'm new to remoting concepts . i have develop an appliction using vb.net remoting .. thats send a form from client to server and vice versa .. will u suggest me how to learn remoting concepts and start programming basically in short time

re: Remoting?

William — Tue, 28 Sep 2004 21:04:00 GMT

I use CAO almost exclusively. I don't look at Remoting as a "way to execute a message on a server", ala Web Services. I see it as a way to have, well, remote objects. Of course, this is from writing things for a casino and a payment processing system, where I don't trust the clients to even give the time of day.

Tricky Exception Message while Remoting...

TrackBack — Sun, 26 Sep 2004 21:49:00 GMT

re: Remoting?

William — Sun, 26 Sep 2004 20:36:00 GMT

Ok, that pretty much confirms what I thought - CAO's are useful but their usefulness is pretty specific. Thanks for the links!

re: Remoting?

William — Sun, 26 Sep 2004 19:44:00 GMT

The default is *not* to use CAO. I use CAOs for IPC scenarios only. Even in that case you have to decide if you want your clients to see a server as a service or as an interactive object model. In the former case don't use CAO. In the latter case use CAOs and be aware of the perf hit of chatty calls.

An example implementation I have is where the client can be configured (via config file) to run the server in-proc or hosted out-of-proc. I believe choosing CAO is what enabled this scenario: the server is just another class library not any magic singleton or single-call service.

BTW, if you are getting into remoting, apart from Ingo's site, these two blogs might be useful if you haven't discovered them already (if you know of any others do share :-):
http://blogs.msdn.com/mattavis/
http://blogs.msdn.com/manishg/

re: Remoting?

William — Sun, 26 Sep 2004 17:42:00 GMT

Daniel:

Thanks man, and yes, I definitely see your point. I asked Michael this and figured I'd run it by you. In comparison, how much of each do you use, like the ratio of using SAO's to CAO's on the whole? Do you find yourself using one over the other a lot more, or is it pretty much evenly distributed?

Thanks again,

Bill

re: Remoting?

William — Sun, 26 Sep 2004 17:41:00 GMT

Michael:

Thanks for the reply. I understand that state management is the primary reason for using CAO's but doesn't using them the same way you would a 'normal' object increase the overhead substantially. I guess what i'm asking is say I have a remoting layer and an object that has StartDoingSomething() and StopDoingSomething(). In that object, if something changes I write to an event log or something of the sort that effectively sends a notification that I or another process/object etc can respond to. So from my client I just treat this layer as essentially a service facade and just concern myself w/ it but not really its state at all. Let's say that StartDoingSomething does all kinds of stuff,creates a Foo(), a Bar() and they raise all sorts of events and everything else, just like I normally would. So basically all of this processing is happening on the app server and all the object managment is essentially happening there. This is pretty much the scenario that I've dealt with so far (again, I'm only a month into using Remoting so that's why I ask - this definitely isn't the voice of experience.) So now, how would I use CAO's to enhance or add a good twist to it? If I make Foo and Bar CAO's then I'm dealing with them directly which requires a lot more maintenance, at least as far as I understand it - doesn't it?

Actually, let me rephrase it (and from reading your blog [particularly the entry about Hiring/Interviewing] I know you are pretty well versed with this) - In comparison, what would you say the ratio of your SAO to CAO usage is? Is it pretty even or is it weighted one way or the other? Do you prefer to work with one over the other?

Thanks again, I definitely appreciate it/

re: Remoting?

William — Sun, 26 Sep 2004 14:33:00 GMT

I use CAO to have an easy way to maintain state in a remoted object, when the state must be maintained by the server.

re: Remoting?

William — Sun, 26 Sep 2004 12:15:00 GMT

Have you ever done ActiveX EXE (out-of-proc COM)? If you are trying to replace that out-of-proc communication in the .NET world you would do remoting. In that scenario CAO is what you would probably use (every client object talks to a corresponding server object and their lifetimes are usually linked). Not sure if that helps you "get it" but I though I'd chime in.