Hans Leidekker <[EMAIL PROTECTED]> writes in gmane.comp.emulators.wine.devel:
> On Friday 18 July 2008 16:11:37 Dan Kegel wrote:
>
> > Building winhttp on top of wininet lets us develop on trunk and
> > is probably the fastest path to making a bunch of applications
> > happy, isn't it? That's t
On Friday 18 July 2008 16:11:37 Dan Kegel wrote:
> Building winhttp on top of wininet lets us develop on trunk and
> is probably the fastest path to making a bunch of applications
> happy, isn't it? That's the way I'm leaning, anyway.
True, but that's been tried already:
http://www.mail-archi
James Hawkins wrote:
> On Fri, Jul 18, 2008 at 9:11 AM, Dan Kegel <[EMAIL PROTECTED]> wrote:
>> James wrote:
>>> I thought the idea was to implement winhttp and then
>>> implement wininet on top of winhttp. Why are you importing wininet?
>> As of January, Hans was still talking about implementing
On Fri, Jul 18, 2008 at 9:11 AM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> James wrote:
>> I thought the idea was to implement winhttp and then
>> implement wininet on top of winhttp. Why are you importing wininet?
>
> As of January, Hans was still talking about implementing
> winhttp on top of winin
James wrote:
> I thought the idea was to implement winhttp and then
> implement wininet on top of winhttp. Why are you importing wininet?
As of January, Hans was still talking about implementing
winhttp on top of wininet
( http://www.winehq.org/pipermail/wine-devel/2008-January/062172.html
http:/
On Friday 18 July 2008 05:45:15 James Hawkins wrote:
> I thought the idea was to implement winhttp and then implement wininet
> on top of winhttp. Why are you importing wininet?
wininet on top of winhttp is the most promising option but I don't think
a consensus has been reached yet.
A technica
On Thu, Jul 17, 2008 at 7:37 PM, Zac Brown <[EMAIL PROTECTED]> wrote:
> Setup winhttp.h and wininet.h with type guards to allow for use of wininet.h
> in winhttp implementation.
>
> --snip--
>
> Note: I am unsure of whether its better to do this, or finish up winhttp.h
> and then create a private h
