slwqw
驱动大牛
驱动大牛
  • 注册日期2002-07-18
  • 最后登录2016-01-09
  • 粉丝0
  • 关注0
  • 积分7分
  • 威望197点
  • 贡献值0点
  • 好评度147点
  • 原创分0分
  • 专家分0分
阅读:1213回复:0

TDI 9X : DDK的说明怎么自相矛盾??? (或者是我不能正确理解???)

楼主#
更多 发布于:2003-12-28 10:41
第一部分:

Comments

[   A pointer to a TDI_REQUEST structure is passed into every VxD TDI call   ]. The VxD TDI client must fill in the structure before invoking the VxD. The handle field will contain either an address object handle or a connection context, depending on the call. The RequestNotifyObject field is set to be a pointer to a client-supplied callback function that TCP will call when the request finally completes, if and only if the request returned TDI_PENDING when it was first invoked. Note that a callback can happen before the call to the function returns. The RequestContext field will be passed back unchanged as a parameter to the callback function when it is called. The TdiStatus field is unused.

Following is the prototype for the callback function:

void Callback(
  PVOID Context,
  TDI_STATUS FinalStatus,
  unsigned long ByteCount
);

第二部分:

TDI_STATUS TdiSetEvent(PVOID Handle,
  int Type,
  PVOID Handler,
  PVOID Context
 );
 

难道TdiSetEvent()不算一个VxD Call???

如果TdiSetEvent()不带TDI_REUQEST的话,那如果我在里边返回TDI_ENDING,以后我怎么把操作的最终状态返回给TDI Client???
游客

返回顶部