 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Remoting / June 2007Calling remote object delay
Dear all, I have build a client aplication which gets service from a remote object hosted by a windows service. Everything works fine except one enoying initilaisation part. The problem I got is that when my Server object is running on a remote PC different that the client.The client place a call to a method on the remote object, at that time the windows authentication to validate that the client user as rights on the remote PC and get the token is taking time, more than 30 seconds and during that time my client application is in an idle state of course. is tehr a way to gets that authentication part more quick in a way or should I set something in config files? My remote object work as singleton Thnaks for help regards Serge > is tehr a way to gets that authentication part more quick in a way or > should I set something in config files? The setup time for remoting can be quite long - depending on how much data you're sending across the wire. Are you sending a Serializable object across the wire? Or are you using MarshalByRef? MarshalByRef will only sent a pointer to an object which will reduce data transfer greatly - this is good if you want your remote clients to access large data objects infrequently (if it's frequent access, then you should serialize the object). I am using MarshallByRef ref My remote objects inherit form MArshallByRef, in additin to that my class a the Serialize attribute.. ONe thing is that this time delay is long only during the first call for the remote object function becaus I get it needs to cheks user credential on remote PC. As soon as the first call is made, all others successive call to the server is really fat and do dot have that delay anymore. Any ideas ? regards serge > > is tehr a way to gets that authentication part more quick in a way or > > should I set something in config files? [quoted text clipped - 7 lines] > to access large data objects infrequently (if it's frequent access, then > you should serialize the object). > I am using MarshallByRef ref > My remote objects inherit form MArshallByRef, in additin to that my > class a the Serialize attribute.. Remove the serialize attribute - I believe if it is there, it will serialize the object and send it across the wire. > ONe thing is that this time delay is long only during the first call > for the remote object function becaus I get it needs to cheks user > credential on remote PC. > > As soon as the first call is made, all others successive call to the > server is really fat and do dot have that delay anymore. The initialization (connect) in remoting does take a while ... Usually this is related to transferring fo the intial serialized objects. Thnaks for your reply I remove the Serialize attribute but no help..same delay when server and client are runing on different PC. I think that it is also part of the Autentication process... If we can do nothing agains that, then I have to accept it.... Will it help if I change the mode of my remote object regards serge > > I am using MarshallByRef ref > > My remote objects inherit form MArshallByRef, in additin to that my [quoted text clipped - 12 lines] > The initialization (connect) in remoting does take a while ... Usually this > is related to transferring fo the intial serialized objects. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.