> Browsing through
>http://www.squid-cache.org/Versions/v2/2.7/cfgman/
> and the 2.6 manual, it seems like the argument types for all config
> directives are missing... has something changed?
>
>
> --
> Mark Nottingham m...@yahoo-inc.com
>
I don't think the argument types have ever been
Browsing through
http://www.squid-cache.org/Versions/v2/2.7/cfgman/
and the 2.6 manual, it seems like the argument types for all config
directives are missing... has something changed?
--
Mark Nottingham m...@yahoo-inc.com
* Remove isImported. Copy and then free the buffer when importing
instead. Same motivation as in the isLiteral comment above.
>>> This too has a IMO a very practical use: it allows us an easy path to
>>> get into the SBuf world i/o buffer which have been created by the i/o
>>> layer.
On 03/04/2009 06:09 AM, Kinkie wrote:
> Who'd be in charge of managing the passed memory block?
> I see two choices:
> - the caller is in charge
> then absorb becomes an alias of assign() and has no reason to exist
> except create confusion
> - absorb frees
> this would make the behaviour more
>>> * Remove isImported. Copy and then free the buffer when importing
>>> instead. Same motivation as in the isLiteral comment above.
>>>
>> This too has a IMO a very practical use: it allows us an easy path to
>> get into the SBuf world i/o buffer which have been created by the i/o
>> layer. If yo
