Remoting question

Question

Hello I have a remote object that I configure first and then register to the remoting service. No matter if I use Singleton or Singlecall as the WellKnownObjectMode when my client program calls one of the methods on this remote object new instance of MyRemoteObject is created and the method on this new instance is called. Of course with singleton mode new instance is created only once but it still isn't the one I just configured and registered. This bothers me because I want to call the very instance of MyRemoteObject I just CONFIGURED and registered to the remoting service. I don't wan to create new instance of the remote object every time it's method is called(or once with singleton mode). How can this be done so that the very instance that I configured and registered is invoked when client calls it's method? //I create new instance of my remote object MyRemoteObject myObj = new MyRemoteObject(); //I configure the object myObj.configure(); //Then register it to the remoting service TcpChannel tcpChan = new TcpChannel(8080); ChannelServices.RegisterChannel(tcpChan); RemotingConfiguration.RegisterWellKnownServiceType( myObj.GetType() myObj.GetType().NameWellKnownObjectMode.Singleton); Thanks in advance kerkkoj.

shimtanny · Answer

Hi I'm sorry but i think i cannot give you a appropriate answer. Maybe you can contact Ingo Rammer from Think Tecture: http://www.thinktecture.com/ I found also a PDF with some guidlines (on their website)... but its not exactly what i've searched. Maybe threads with a threadpool? Could be the right one. I think creating every time a new thread manually costs to much. A threadpool (FCL) is configurable about number of threads etc. Cheers Simon

kerkkoj · Answer

Yes thank you wery much! Can you help me a bit more how can I make this type of remoting scenario scalable for multiple concurrent clients? Should I kick new thread up every time this singleton remote instance is called or should I use delegates and asynchronous remoting?

shimtanny · Answer

Hi It's possible the following way: // Create remote object which is not shared at the moment. RemoteObject remObj = new RemoteObject(); // Configure remote object. remObj.Configure(); // Create and register channel. ChannelServices.RegisterChannel(new TcpChannel(8080)); // Now register your remote object as a well known service type. // URI: tcp://localhost:8080/RemoteObject RemotingServices.Marshal(remObj RemoteObject); This way you can only have Singleton remote objects but as i see this is what you wannt. Hope i helped. Cheers Simon