What’s next on the client HTTP stack front


http://www.microsoft-watch.com/article2/0,2180,1940567,00.asp
Hachamovitch acknowledged Microsoft already is building the next two versions of IE. He declined to offer guidelines on delivery schedules or feature sets, other than to say one of the two versions will include “a complete reworking of the networking stack.”


That would be us. We are going to be busy for awhile 🙂


— Ari Pernick

Comments (6)

  1. PatriotB says:

    Wow.  That’s pretty big news!

    Could it be switching IE to use WinHTTP?  Either directly, or by reworking WinInet to be a front end for WinHTTP?

  2. EricLaw [MSFT] says:

    Nope, IE won’t be using WinHTTP either.  When Dean said "a complete reworking", he meant it.  🙂

  3. A bit off-topic, my apologies…

    Ari, you <a href="http://news.thedigitalmachine.com/2006/04/25/microsofts-shoddy-http-api/#comment-418">posted a note</a> that there was an updated WinINet Async sample.  Is that code available?  I only see one unrelated download on the WNDP Connect site.  

    I was unclear about if the new sample code is paired with WinInet improvements only available under Vista.  Will it compile and/or run in older environments?

    Thanks again.

  4. Ari Pernick says:

    Sorry about that, we did a last minute code review and found that the sample needed a little more work. The sample we will put out is not exclusive to the WinInet shipping with IE7 or Windows Vista.

  5. As we&amp;nbsp;begin the&amp;nbsp;planning phase for our &quot;Next Generation&quot; client&amp;nbsp;HTTP stack, we would love…