This is a tough choice you always have to make . Choice 1 - Use fast binary tcp connection , in which case you have to do the security yourself. eg send a hash of the userID with every request if you want high security.
Choice 2 - use non binary connection and .NET can do it for you . EJB 1.3+ spec uses something similar to Choice 2 , but binary tcp connections can send information twice as fast. And getting a 100% performance gain on bottleneck always sways my choices over nice code , but it depends on your requirements. Ben -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Henderson Sent: Tuesday, 11 June 2002 1:58 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Secure remoting... Is there a standard way for securing a remoting connection so a remoted object can obtain the users identity/principal from the client/consumer of the remoted object - In java terms something along the lines of the "Common Secure Interoperability" features of the EJB 1.3+ spec. Cheers, - Alex You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
