From: Jason O'Broin [jason@windriver.com] Sent: Friday, October 27, 2000 2:50 PM To: NT Developers Interest List Subject: [ntdev] Re: TDI Question > ----- Original Message ----- > From: justin white > Thanks, > I have found that the TDI filtering is quite messy. I also save the > original address object in my event handler and so can easily get to it > when my event is called. Unfortunately the ConnectionContext receive > in the call does not correlate to any other context I 'see' > previously (like from a TDI_CONNECT for instance). This also leads to > my next question, why is TDI_ASSOCIATE_ADDRESS not always called. > According to the TDI spec, it should be called. I came across this case recently, and I suspect this is what you are seeing. Connection endpoints created for use accepting connections are NOT pre-bound to an address object. Typically, the transport will call the client's ClientEventConnect handler. The reply to this function call is a TdiAccept IRP AND a ConnectionContext value, AND this IRP is directed to one of the unbound endpoints setup earlier --- ie. the client supplies the endpoint that it wants the incoming connection to be bound to. As the ClientEventConnect function that is called is registered by TdiSetEvent with an Address object, the endpoint that the client uses in the returned TdiAccept message is implicitly associated with this address object. And your right, the docs are seriously unclear on this point. Hope that helps. Jason -- Jason O'Broin, Member of Technical Staff, Server Products Group Wind River Networks, 500 Wind River Way, Alameda, CA 94501-1147 USA Phone: +1 (510) 749 2466 Fax: +1 (510) 749 2914 Email: jason@wrs.com --- You are currently subscribed to ntdev as: GlennEverhart@FirstUSA.com To unsubscribe send a blank email to leave-ntdev-247T@lists.osr.com