Hans Leidekker wrote:
> On Wednesday 02 July 2008 23:56:51 Rob Shearman wrote:
>
>> How about:
>> 3) Copy the networking sublayer from wininet into winhttp and build on top
>> of that to implement winhttp. Reimplement wininet on top of winhttp.
>
> Drawback to this option is that you're going to
On Wednesday 02 July 2008 23:56:51 Rob Shearman wrote:
> How about:
> 3) Copy the networking sublayer from wininet into winhttp and build on top
> of that to implement winhttp. Reimplement wininet on top of winhttp.
Drawback to this option is that you're going to destabilize wininet, but
perhaps
2008/7/1 Zac Brown <[EMAIL PROTECTED]>:
> I've been looking at implementing winhttp.dll.
>
> My current two ideas are to either:
> 1) Copy the networking sublayer from wininet into winhttp and build on top of
> that to implement winhttp. Effectively reimplementing mostly from scratch.
>
> 2) Implem
Hans Leidekker wrote:
> On Tuesday 01 July 2008 21:42:30 Zac Brown wrote:
>
>> Does anyone have thoughts on implementing parts of winhttp in terms of
>> wininet? The primary issue that prevents entirely implementing winhttp in
>> terms of wininet is that there is no direct Win32 API for fetching a
On Tuesday 01 July 2008 21:42:30 Zac Brown wrote:
> Does anyone have thoughts on implementing parts of winhttp in terms of
> wininet? The primary issue that prevents entirely implementing winhttp in
> terms of wininet is that there is no direct Win32 API for fetching an SSL
> certificate in winhtt
Hi,
I've been looking at implementing winhttp.dll.
Does anyone have thoughts on implementing parts of winhttp in terms of wininet?
The primary issue that prevents entirely implementing winhttp in terms of
wininet is that there is no direct Win32 API for fetching an SSL certificate in
winhttp.
