W3C home > Mailing lists > Public > www-lib@w3.org > July to September 2000

RE: Solution for possible crash if using SSL

From: Kallweit, Heiner <Heiner.Kallweit@commerzbank.com>
Date: Wed, 26 Jul 2000 17:46:16 +0200
Message-ID: <01EBDB2D6DFDD211A98200805FF50CF901188D66@SV002871>
To: "'jose.kahan@w3.org'" <jose.kahan@w3.org>
Cc: "'www-lib@w3.org'" <www-lib@w3.org>
1. You're right, it blocks every flush. It was a quick fix for me
   and in my app there is always only one host. So it may not be a
   solution for everybody.
2. To use the forceWriteFlush-flag is IMHO no good idea, because
   this flag is set also at other places in HTHost.c and we had
   no chance to reset the flag. So we have to add a new flag to
   the HTHost structure ?

Regards, Heiner

> -----Ursprüngliche Nachricht-----
> Von: jose.kahan@w3.org [mailto:jose.kahan@w3.org]
> Gesendet am: Mittwoch, 26. Juli 2000 17:21
> An: Kallweit, Heiner
> Cc: 'www-lib@w3.org'
> Betreff: Re: Solution for possible crash if using SSL
> Hello Heiner,
> I saw your patch. One thing that worries me is that your patch blocks
> all flushes that may be done in any host. Did you try to use the
> host->forceWriteFlush variable instead, to do the same thing?
> That is
> if (host->force_writeFlush || targetNet == NULL)
> instead of
> if (in_flush || targetNet == NULL)
> It looks like a better solution to me. Could you give it a 
> try and then
> report back to the list?
> Thanks!
> -Jose
Received on Wednesday, 26 July 2000 11:46:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:37 GMT