problems about remoting singleton

[=?Utf-8?B?ZmFpcnl2b2ljZQ==?=]

we know that if the type is registered as singleton in the host side, then
all the remoting clients share one object, like:
host:
=====
TcpServerChanne l chn = new TcpServerChanne l(9999);
ChannelServices .RegisterChanne l(chn,true);

RemotingConfigu ration.Register WellKnownServic eType(typeof(So meClass),
"someclass",Wel lKnownObjectMod e.SingleCall);
========

client:
===========
SomeClass a = (SomeClass)Acti vator.GetObject (typeof(SomeCla ss),
@"tcp://172.16.64.190:9 999/mul");
===========

now that all the remoting clients share one object, is there anyway i can
capture this object shared by the client? or can i just "new" an object and
then register this very object instead of the type of it on the host side so
i can control the state and behavior of it.

thankx

[=?Utf-8?B?Q2lhcmFuIE8nJycnRG9ubmVsbA==?=]

Not entirely sure about the answer to your question (although I will look),
however, the line:
RemotingConfigu ration.Register WellKnownServic eType(typeof(So meClass),
"someclass",Wel lKnownObjectMod e.SingleCall);
doesnt make a singleton. The WellKnownObject Mode.SingleCall means one per
client. WellKnownObject Mode.Singleton means one shared object
--
Ciaran O''''Donnell
http://wannabedeveloper.spaces.live.com
"fairyvoice " wrote:

we know that if the type is registered as singleton in the host side, then
all the remoting clients share one object, like:
host:
=====
TcpServerChanne l chn = new TcpServerChanne l(9999);
ChannelServices .RegisterChanne l(chn,true);

RemotingConfigu ration.Register WellKnownServic eType(typeof(So meClass),
"someclass",Wel lKnownObjectMod e.SingleCall);
========

client:
===========
SomeClass a = (SomeClass)Acti vator.GetObject (typeof(SomeCla ss),
@"tcp://172.16.64.190:9 999/mul");
===========

now that all the remoting clients share one object, is there anyway i can
capture this object shared by the client? or can i just "new" an object and
then register this very object instead of the type of it on the host side so
i can control the state and behavior of it.

thankx

[=?Utf-8?B?Q2lhcmFuIE8nJycnRG9ubmVsbA==?=]

I cant see anything from the framework to do this but one easy answer is to
have a static property on the server type which each instance sets to itself
on activation. For a singleton, there should only be one so it should work
nicely. Then you can access this property on the server. You will need to
ensure thread safety on all methods and properties though.
--
Ciaran O''''Donnell
http://wannabedeveloper.spaces.live.com
"fairyvoice " wrote:

we know that if the type is registered as singleton in the host side, then
all the remoting clients share one object, like:
host:
=====
TcpServerChanne l chn = new TcpServerChanne l(9999);
ChannelServices .RegisterChanne l(chn,true);

RemotingConfigu ration.Register WellKnownServic eType(typeof(So meClass),
"someclass",Wel lKnownObjectMod e.SingleCall);
========

client:
===========
SomeClass a = (SomeClass)Acti vator.GetObject (typeof(SomeCla ss),
@"tcp://172.16.64.190:9 999/mul");
===========

now that all the remoting clients share one object, is there anyway i can
capture this object shared by the client? or can i just "new" an object and
then register this very object instead of the type of it on the host side so
i can control the state and behavior of it.

thankx

[=?Utf-8?B?ZmFpcnl2b2ljZQ==?=]

1.do you mean that i design the server type as a singleton (using the
singleton pattern as showned in the book of GOF)?
2.it is really my stupid mistake the the codes given previous, i actually
meant WellKnownObject Mode.Singleton