Re: server auto-identification of the clients after authenfication
- From: Spam Catcher <spamhoneypot@xxxxxxxxxx>
- Date: Mon, 06 Nov 2006 05:49:34 GMT
baramuse@xxxxxxxxx wrote in news:1158223843.193282.71910
@e3g2000cwe.googlegroups.com:
when the client authentificate with the server (with a login/password)
the server would keep something that could distinguish this client from
the other (that's what i'm looking for, perhaps an channl identifier?)
and when that client would call other methods on the server object, the
server will be able to identify the client to give it the good
stuff....
Depending on how you authenticate the user, the user information, the login
information can be retrieved via the Thread Principal.
If the Thread Principal is not available, a simple way of saving log in
information on a per call basis is to use the CallContext object. However,
the CallContext works on a per thread basis so you'll have to set it each
time for each thread.
Otherwise you could create a custom channel which stores your log in
information in a custom principal object - which would be the ideal way of
storing log in information.
Also take a look at Geniune Channels - their channels have the
login/credentials portion all built.
.
- Prev by Date: Re: server auto-identification of the clients after au ...
- Next by Date: Remoting large dataset - deserialization is slow
- Previous by thread: Re: server auto-identification of the clients after au ...
- Next by thread: Remoting large dataset - deserialization is slow
- Index(es):
Relevant Pages
|