TLS profile and session object

Hi,
I have two parties communicating over a BEEP session. There are 2 
channels, in operation. One initiated by one party, the other initiated 
by the other.
Once hte session is established I'd like to:
negotiate TLS,
Pary A opens one channel
Party B opens the other

Everything works fine without TLS, however when either party starts the 
TLS negotiation, the other party doesn't know its going on. 
Consequently, the send their start channel message with the OLD session 
object. This seems to result in the start channel message being sent in 
plaintext. The other party is expecting this message to be sent 
encrypted, and so of course cannot understand its contents.

I'm starting TLS using:
TLSProfile.getDefaultInstance().startTLS(session)).

The other party is just doing a listen for a TCP session connection and 
then doing a sessoin.startChannel() call to start the session (which is 
occuring in plaintext).

Is there a way I can get the guy who doesn't start TLS to update his 
session object to reflect the fact that TLS is now going and that 
requests should be sent encrypted?

Thanks
Toby



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com