From: Thomas F. Divine [tdivine@pcausa.com] Sent: Thursday, October 26, 2000 12:38 PM To: NT Developers Interest List Subject: [ntdev] Re: TDI Question ----- Original Message ----- From: justin white To: NT Developers Interest List Sent: Thursday, October 26, 2000 12:18 PM Subject: [ntdev] Re: TDI Question > Thank you very much for the assistance, > ... > The ConnectionContext is however merely passed as a type CONNECTION_CONTEXT to the event handlers, which is defined as a type PVOID. My question is therefore, what does this ConnectionContext mean to the client, and how can i use it to associate this Event Handler with a particular connection endpoint. Perhaps I am looking at the inappropriate variables, but this seems to be the only one relating back to the original connection end-point. > To answer this question you simply have to look from the perspective of a TDI Client. Basically, the client can use the PVOID for any purpose desired. It's his, and TDI will give it back when it's needed. More then likely it's just a pointer to some internal structure that the TDI client keeps around for it's own use. There are no rules for what the TDI client might use the field for, so no way to interpret it safely... In my filters I always substitute my own value for this context and stash the original caller's value. So, In my hook function callbacks I know what CONNECTION_CONTEXT means to ME. If the call is passed on upwards I fetch the stashed original context and give him that. Sorry, Thomas --- You are currently subscribed to ntdev as: GlennEverhart@FirstUSA.com To unsubscribe send a blank email to leave-ntdev-247T@lists.osr.com