> Sorry, but I can't see how this can fix anything. The 'data' pointers
> should be pointing to the *same* struct for both connections. The
> connections are but two structs using the same base SessionHandle
> struct!

OK. Now I understand. The problem appeared within my patch.
For 3rd party transfer, there is a need to keep 2 'data' structs
(SessionHandle), one for each connection. So in ConnectionExists(), if
there is more than one open connection, conn_temp will be pointed to
some connection in data->state.connects, but the 'data' won't be the
same. Therefore refreshing the user data ('set' struct) in the primary
connection will solve the problem. Do you have any other way to handle
this?

The information contained in this message is proprietary of Amdocs,
protected from disclosure, and may be privileged.
The information is intended to be conveyed only to the designated recipient(s)
of the message. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, use, distribution or copying of
this communication is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.
Thank you.
Received on 2004-06-01