<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That’s unfortunate. Where is the caching taking place?<div class=""><br class=""></div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Sep 9, 2015, at 8:04 PM, Bruno Jesus <<a href="mailto:00cpxxx@gmail.com" class="">00cpxxx@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Wednesday, September 9, 2015, Matt Durgavich <<a href="mailto:mattdurgavich@gmail.com" class="">mattdurgavich@gmail.com</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why are we looking at the dll side again?<br class=""></blockquote><div class=""><br class=""></div><div class="">Closing the sockets server side does not clear the ntdll cache, the current solution is incomplete then as functions like send and closesocket will fail for the wrong reasons because the socket is still "available".</div><div class=""><br class=""></div><div class="">Best regards, </div><div class="">Bruno</div>
</div></blockquote></div><br class=""></div></div></body></html>