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

RE: making libwww thread-safe

From: Andy Levine <andyl@epicrealm.com>
Date: Tue, 18 Jul 2000 07:47:00 -0500
To: <www-lib@w3.org>
Cc: "Martin Ostrowski" <Martin.Ostrowski@bov.de>
Message-ID: <000701bff0b6$43cf0ca0$0301a8c0@c868461-a.infospinner>
Matthias,

You CAN do it, but it is some work. The way I did it was to create one
thread whose job was the requestor thread. ALL interfacing to libwww is done
within the context of this thread. Then all requests are queued into this
thread, which wakes up when there is "work to do", i.e. make a request, test
the completion status of a request, etc.

Andy

> -----Original Message-----
> From: www-lib-request@w3.org [mailto:www-lib-request@w3.org]On Behalf Of
> Martin Ostrowski
> Sent: Tuesday, July 18, 2000 4:39 AM
> To: 'www-lib@w3.org'
> Subject: making libwww thread-safe
>
>
> Hi,
>
> i've followed the "is libwww thread safe"-Discussion in this list.
> we also have the challenge to provide a multithreaded Bot.
> The only task of this Bot is to connect a Webserver and return the Content
> via CORBA to another Process...
>
> We want to do this the multithreaded-Way, because the fork() is not
> available under NT
> and the equivalent Functions are very expensive...
>
> Are there any experiences with this Problem or other Ideas ?
>
> Thanx in Advance
>
> Matthias Koch
>
>
>
>
Received on Tuesday, 18 July 2000 08:51:23 GMT

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