simple remoting

[Tom]

just a general question

why is it in remoting that sometimes people use a client, a server and a
service (serialised) class that stores the server return value to pass to
the client ?

what I don't understand is why people use the serialised service class when
they can simply use a interface on the client side and call the server
methods directly...

thanks
Tom

[Stoitcho Goutsev \(100\) [C# MVP]]

Hi Tom,

Eventually you are always need to serialize some data. You can use
functionality via interfaces, but if you want to communicate data interfaces
won't help. See even if you have interface with property for each piece of
data the actual values have to be serialzed.

The other diference is that when you use intefaces and MarshalByRef objects
the actual instance operates in the context of the server application (here
..Net Remoting lifetime service comes into play as well). With serialization
all the method are executed by the client and work in its environment. There
the lifetime service has no place as long as everythinng is controlled by
the GC as for any local object.
--
HTH
Stoitcho Goutsev (100) [C# MVP]
"Tom" <to********@optushome.com.au> wrote in message
news:41***********************@news.optusnet.com.a u...

just a general question

why is it in remoting that sometimes people use a client, a server and a
service (serialised) class that stores the server return value to pass to
the client ?

what I don't understand is why people use the serialised service class
when
they can simply use a interface on the client side and call the server
methods directly...

thanks
Tom

[Tom]

thanks for explaining :D

"Stoitcho Goutsev (100) [C# MVP]" <10*@100.com> wrote in message
news:O#**************@TK2MSFTNGP09.phx.gbl...

Hi Tom,

Eventually you are always need to serialize some data. You can use
functionality via interfaces, but if you want to communicate data interfaces won't help. See even if you have interface with property for each piece of
data the actual values have to be serialzed.

The other diference is that when you use intefaces and MarshalByRef objects the actual instance operates in the context of the server application (here .Net Remoting lifetime service comes into play as well). With serialization all the method are executed by the client and work in its environment. There the lifetime service has no place as long as everythinng is controlled by
the GC as for any local object.
--
HTH
Stoitcho Goutsev (100) [C# MVP]
"Tom" <to********@optushome.com.au> wrote in message
news:41***********************@news.optusnet.com.a u...

just a general question

why is it in remoting that sometimes people use a client, a server and a
service (serialised) class that stores the server return value to pass to the client ?

what I don't understand is why people use the serialised service class
when
they can simply use a interface on the client side and call the server
methods directly...

thanks
Tom