Remoting question
-
Hi all. This is the first time I'm tackling a remote application so I got a few doubts I wanna get straightened out before I get into it. The first question that comes to mind is: what is the cost of keeping a registered channel during the client application's life. I mean, is it worth it to register and unregister a tcp channel everytime I call the remote object or is registering a channel when the app starts and closing it only when the user exits the client application a good enough solution? Thanks
-
Hi all. This is the first time I'm tackling a remote application so I got a few doubts I wanna get straightened out before I get into it. The first question that comes to mind is: what is the cost of keeping a registered channel during the client application's life. I mean, is it worth it to register and unregister a tcp channel everytime I call the remote object or is registering a channel when the app starts and closing it only when the user exits the client application a good enough solution? Thanks
I bet the cost of registering and unregistering the channel is going to cost you more than the channel itself. In fact its not necessary to explicitly unregister the channel when the app closes. Framework will take care of that for you. I would worry more about object lifetimes. From what you're saying it sounds like you are doing single call - you shouldn't have any problems. This posting is provided "AS IS" with no warranties, and confers no rights. Alex Korchemniy
-
I bet the cost of registering and unregistering the channel is going to cost you more than the channel itself. In fact its not necessary to explicitly unregister the channel when the app closes. Framework will take care of that for you. I would worry more about object lifetimes. From what you're saying it sounds like you are doing single call - you shouldn't have any problems. This posting is provided "AS IS" with no warranties, and confers no rights. Alex Korchemniy
Thanks for the input Alex. Yes, my remote object will be a single call object and wont need to be a client activated object with state info, so I wont have to worry about the objects lifespan. I'll register a client channel upon the client app's start and keep that one throughout it's whole life.