locked
During processing data at stream layer. RRS feed

  • Question

  • Hi, guys.

    I have a problem when WHCK test (callout driver).

    During processing data at stream layer,

    it seems that resource release event have occurred for the connetion without closing endpoint.

    Is this the correct way?

    If so, can I pend the resource release event like endpoint closur event?

    Or is it trouble that using resource address handle at stream layer?

    Thanks.

    Thursday, February 21, 2013 5:52 AM

Answers

  • RESOURCE_RELEASE is meant to be a notification layer.  You cannot pend this.  ENDPOINT_CLOSURE is meant to allow the closure of the endpoint to be held off until all data is injected.  You can pend @ endpoint closure.

    Hope this helps,


    Dusty Harper [MSFT]
    Microsoft Corporation
    ------------------------------------------------------------
    This posting is provided "AS IS", with NO warranties and confers NO rights
    ------------------------------------------------------------

    Thursday, February 21, 2013 8:00 PM
    Moderator

All replies

  • RESOURCE_RELEASE is meant to be a notification layer.  You cannot pend this.  ENDPOINT_CLOSURE is meant to allow the closure of the endpoint to be held off until all data is injected.  You can pend @ endpoint closure.

    Hope this helps,


    Dusty Harper [MSFT]
    Microsoft Corporation
    ------------------------------------------------------------
    This posting is provided "AS IS", with NO warranties and confers NO rights
    ------------------------------------------------------------

    Thursday, February 21, 2013 8:00 PM
    Moderator
  • Thanks your reply, Dusty.

    You mean RESOURCE_RELEASE can be called any time regardless of ENDPOINT_CLOSURE, right?

    Thanks again...

    Monday, February 25, 2013 6:15 AM
  • Generally well behaved sockets will see ENDPOINT_CLOSURE first, and RESOURCE_RELEASE later.  When the system is alerted that the socket has been "unbound", then RESOURCE_RELEASE is invoked.

    This may help you further:

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff543748(v=vs.85).aspx

    Hope this helps,


    Dusty Harper [MSFT]
    Microsoft Corporation
    ------------------------------------------------------------
    This posting is provided "AS IS", with NO warranties and confers NO rights
    ------------------------------------------------------------

    Wednesday, February 27, 2013 8:05 PM
    Moderator