[Prev][Next][Index][Thread]
HTRequest parameter on HTEvent_Loop?
-
To: www-lib-bugs@w3.org
-
Subject: HTRequest parameter on HTEvent_Loop?
-
From: Henrik Frystyk Nielsen <frystyk@w3.org>
-
Date: Wed, 15 May 1996 11:51:36 -0400
-
From frystyk@w3.org Wed May 15 11: 51:39 1996
-
Message-Id: <199605151551.LAA01068@www20.w3.org>
-
Reply-To: Henrik Frystyk Nielsen <frystyk@w3.org>
-
X-Mailer: exmh version 1.6.7 5/3/96
------- Forwarded Message
Return-Path: msa@msa.tte.vtt.fi
Return-Path: <msa@msa.tte.vtt.fi>
Received: from www10.w3.org by www20 (5.0/NSCS-1.0S)
id AA16296; Thu, 29 Feb 1996 07:36:51 -0500
Received: from msa.tte.vtt.fi by www10.w3.org (5.0/NSCS-1.0S)
id AA20484; Thu, 29 Feb 1996 07:36:49 +0500
Received: (from msa@localhost) by msa.tte.vtt.fi (8.7/8.7) id OAA12887; Thu,
29 Feb 1996 14:33:52 +0200 (EET)
Date: Thu, 29 Feb 1996 14:33:52 +0200 (EET)
From: Markku Savela <msa@msa.tte.vtt.fi>
Message-Id: <199602291233.OAA12887@msa.tte.vtt.fi>
To: frystyk@w3.org
Subject: HTRequest parameter on HTEvent_Loop?
Reply-To: msa@hemuli.tte.vtt.fi (Markku Savela)
Content-Type: text
Content-Length: 1248
Hi,
I decided not to bother the www-lib list with this detail...
I am wondering if the HTRequest parameter in HTEvent_Loop is sensible.
It doesn't seem to be used for anything until some error occurs. My
wonderings are
- which HTRequest is supposed to go with HTEvent_Loop?
- if I use a request created for the purpose of some initial
HTLoadAnchor, there is a problem that this one special HTRequest
cannot be deleted after the load is completed (because the pointer
to it will remain in the HTEvent_Loop, and might get used on error
condition...)
- I have not looked closely, but do the errors that actually use the
HTRequest in event loop really have any relation to this particular
HTRequest?
- maybe event loop description should just state that create a dummy
HTRequest for the purpose, don't use any "real" HTRequest?
With the current library (4.0), I suppose the Event loop would mostly
work if I just passed NULL, but if I decide on that solution, some
future library may barf on my application.
(All this is inspired by the fact that I don't always have any
"natural" HTRequest to pass to HTEvent_Loop in my application, and I
started wondering which of the ones I have would be the right one...)
- -- msa
------- End of Forwarded Message
--
Henrik Frystyk Nielsen, <frystyk@w3.org>
World-Wide Web Consortium, MIT/LCS NE43-356
545 Technology Square, Cambridge MA 02139, USA