Are there any conditions under which the TDI_EVENT_CONNECT handler will
not get called though it has been set?
If you have a pending TDI_LISTEN I think. It will be completed instead of calling TDI_EVENT_CONNECT.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: Charu Venkatraman
To: Windows System Software Devs Interest List
Sent: Thursday, December 23, 2004 3:32 PM
Subject: [ntdev] TDI_EVENT_CONNECT
Are there any conditions under which the TDI_EVENT_CONNECT handler will not get called though it has been set?
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
So do we essentially have to replicate the functionality of the
TDI_EVENT_CONNECT handler in the TDI_LISTEN too?
For example can I deny an incoming connection in the TDI_LISTEN handler?
I see that my tdi_event_connect handler does not get called when some
applications accept a connection.
Date: Fri, 24 Dec 2004 04:48:09 +0300
From: “Maxim S. Shatskih”
Subject: Re: TDI_EVENT_CONNECT
If you have a pending TDI_LISTEN I think. It will be completed =
instead of calling TDI_EVENT_CONNECT.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com http:</http:>
________________________________
From: Charu Venkatraman
Sent: Thursday, December 23, 2004 6:03 PM
To: ‘xxxxx@lists.osr.com’
Subject: TDI_EVENT_CONNECT
Are there any conditions under which the TDI_EVENT_CONNECT handler will
not get called though it has been set?
“Charu Venkatraman” wrote in message
news:xxxxx@ntdev…
So do we essentially have to replicate the functionality of the
TDI_EVENT_CONNECT handler in the TDI_LISTEN too?
For example can I deny an incoming connection in the TDI_LISTEN handler?
I see that my tdi_event_connect handler does not get called when some
applications accept a connection.
One “problem” with TDI is that it is a very flexible API. For most
operations there are at least two ways to accomplist the same functionality.
For example, TDI_LISTEN or TDI_EVENT_CONNECT can both be use to accept an
incomming connection.
There is no “rule” that says which of the two methods will be used by a
particular TDI client. So, you must deal with all possibilities - including
the possibility that a TDI client will change the way it behaves or use
hybrid combinations of possible operations.
You might get a better feel for the possibilities by writing a few TDI
clients before attempting to write a TDI filter.
Good luck,
Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com