Hi all,

before starting I must say that I'm a remoting beginner so I certainly
didn't assimilate all the tricks of remoting so please be kind ;)

Now here is my interrogation:
I'm working on a client/server architecture for a callcenter software.
The server is the only one connected to the oracle database and all the
different clients (operator/admin...) are "connected" to the server via
remoting (it's the best I've found to communicate between server and
clients, am I doing wrong?).

I've managed to call server-instancied objects, make some events fired
over the network... the basic things :)
Now I was wondering: I must identify all the clients requests to give
them the good informations as they will all share the same
server-instancied object. And I'd like not to pass an id with every
client request so is there a way that the server identify itself the
client (once the client has been authentified) ?
I'm not sure to be clear...
Let me give an example :) :
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....

Hope somebody can understand :s

PS: perhaps i use non-english words and i'm sorry, still working on it
;)

Thanks a lot in advance for your answers/feedback...

Hello i have the same problem.
how did you end up solving it?
---

baramuse@gmail.com wrote in news:1158223843.193282.71910
@e3g2000cwe.googlegroups.com:

[quoted text, click to view]

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