>> I suggest to just skip sending those headers if the contents would be too
>> long, rather than using malloc'ed strings everywhere. It seems wasteful
>
>...and rather than truncate them?
What concerns me is whether it is possible for lynx to encounter a legit
situation in need of long values - perhaps a heavily nested web site or
a cgi with a huge variable requirement.
If we start truncating or dropping information because it is long, then
we may very well have to come back to the situation to resolve it later
anyways. If we are going to be touching the code anyways, would it not
be in best interests to fix things as best as they can be fixed?
--
Larry W. Virden <mailto:[EMAIL PROTECTED]><http://www.usenix.org/events/tcl2k/>
<URL: http://www.purl.org/NET/lvirden/> <*> O-
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
-><-
