<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<span style="white-space: pre;">> This is exactly want i want to
implement. When the client object is <br>
> invoked, It returns a security key which will be needed for any<br>
> subsequent operations until its life time expires. I am not very<br>
> experienced in this but what i need is ability to remember that
key,<br>
> access it priori to invoking login() method. For example, one can<br>
> store the security key into a file, and access it using md5checksum<br>
> to guarantee that no one has changed its content. The question is
how<br>
> to do this<br>
> Kindly assist if you can paste some code snippets of what you think<br>
> will work</span><br>
<br>
Well, the interfaces could look something like this:<br>
<br>
interface SecureServer {<br>
void DoSomething(in long key);<br>
void DoSomethingElse(in long key);<br>
oneway void logout(key);<br>
};<br>
<br>
interface SecureLogin {<br>
void login(in string user, in string pw, out SecureServer server, out
long key);<br>
};<br>
<br>
>From the client, you would find your secure login server (possibly
using the Naming Service), then invoke the following sequence:<br>
<br>
sl->login(user, pw, ss, key);<br>
ss->DoSomething(key);<br>
ss->DoSomethingElse(key);<br>
ss->logout(key);<br>
<br>
In the server, the login method would create a temporary server object
implementing the SecureServer interface and return a handle and a key.
Subsequent calls to that new server object (or an object from a pool)
would include that key for validation. The call to logout would destroy
the object or the key and validated connection.<br>
<br>
If you have a good book on C++ CORBA ("Advanced CORBA Programming with
C++" by Henning and Vinoski is the best for any language imo) then
looking for examples which return iterators will illustrate these
temporary server-side objects.<br>
<br>
My use of the word "secure" is just for illustration; others may point
out possible weaknesses in this approach.<br>
<br>
hth<br>
<br>
- Tom<br>
<br>
</body>
</html>