ASP.NET/C# question
-
I have a server that accepts a socket connections and accepts authentication requests in a specific protocol. I want to use this for an ASP.NET authentication. How can I make my ASP.NET app maintain a single connection to this auth server and send authentication requests to it? I mean a COM object does not seem to be the right way anymore. What is the preferred .NET way of implementing this? Thomas
-
I have a server that accepts a socket connections and accepts authentication requests in a specific protocol. I want to use this for an ASP.NET authentication. How can I make my ASP.NET app maintain a single connection to this auth server and send authentication requests to it? I mean a COM object does not seem to be the right way anymore. What is the preferred .NET way of implementing this? Thomas
I guess the "proper" .NET way of doing this is to write a class that takes the credentials and performs the authentication against the server. You create this object then once and store it in the Application context. But beware you better build this object with sound multithreading capabilities, otherwise this might become a severe performance bottleneck. --Chris
-
I guess the "proper" .NET way of doing this is to write a class that takes the credentials and performs the authentication against the server. You create this object then once and store it in the Application context. But beware you better build this object with sound multithreading capabilities, otherwise this might become a severe performance bottleneck. --Chris
So, what you suggest is that I create the class and initialize it on Application Start and clean it up when the Application quits (I am so new to .NET that I do not know the event names). ok.. So this class would create multiple threads that maintain the session with my authentication server. Sounds fine. Now I have to go about designing it. Thank you Thomas
-
So, what you suggest is that I create the class and initialize it on Application Start and clean it up when the Application quits (I am so new to .NET that I do not know the event names). ok.. So this class would create multiple threads that maintain the session with my authentication server. Sounds fine. Now I have to go about designing it. Thank you Thomas
Well with multithreaded I meant: I can handle multiple requests at the same time. Not that it creates multiple threads itself. Think of 50 users hitting your page concurrently. It would be bad if all had to queue up to be authenticated one after another.