Re: Problems with PUT

At 12:38 26/08/1998 -0500, olga wrote:
>I am using the event loop with the NOCacheClient profile, which is
nonblocking
>(as it is said in the documentation).
>
>The examples I have seen (HTLine, PUT, some other small examples) are showing
>the single request processing. Are there any that do multiple? 
>
>If the callback function deletes the profile and returns HT_LOADED, then
>execution returns from the event loop, but the second call to the function
>(with the same parameters) gives me core dumped.
>
>What is happening is mystery for me - the old profile was deleted and new
>created - why not to work???

First, you should only create a profile once - profiles are basically
setting up libwww to perform a often used set of tasks. Also, filters can
be registered as either local for a single request or global for all requests.

The reason for why you see that it "hangs" is that once you enter the event
loop, you stay there until the application ends. Therefore, if you have
multiple operations to perform then you must call them from within a
handler (like for example your terminate handler).

Henrik
--
Henrik Frystyk Nielsen,
World Wide Web Consortium
http://www.w3.org/People/Frystyk

Received on Thursday, 27 August 1998 15:28:13 UTC