This is expected, since each method call from client->server incurs the entire NTLM/Kerb handshake. Same thing happens in web services.
In the case of remoting, there's a Microsoft sample on MSDN that was announced on the DOTNET-CLR list: http://discuss.develop.com/archives/wa.exe?A2=ind0208C&L=DOTNET-CLR&P=R12086 &I=-3 That provides a pair of client & server sinks you can plug in that will use the native SSPI to setup the secure channel on the first call to a give host, securing subsequent method calls w/o incurring the handshake overhead (much the same as dcom security). Please note that the links mentioned on the above page point to msdn.microsoft.com. There's also a 'secure remoting' sample on gotdotnet.com that was posted by someone at msft, but it's not really secure, since the actual session key is transmitted over the wire. -Mike DevelopMentor http://staff.develop.com/woodring http://www.develop.com/devresources ----- Original Message ----- From: "Michel Liesmons" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 9:05 AM Subject: [ADVANCED-DOTNET] Performance of Secure Remoting over HTTP using the BinaryFormatter > Hi, > > I tested the performance of a client using remoting hosted in IIS over hhtp > and the binary formatter doing one simple call. > Is this possible, a known issue, normal, ... ? > > Thanks for sharing any thoughts. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
