RE: metadata question.

> -----Original Message-----
> From: Henrik Nordstrom [mailto:hno@hem.passagen.se]
> Sent: Monday, 29 January 2001 3:23 AM
> To: Robert Collins
> Cc: squid-dev@squid-cache.org
> Subject: Re: metadata question.
>
>
> My vote:
>
> Put it in the reply structure, filled in by the store when
> the object is
> swapped in.

Ok.
 
> How to manage it in the store is a tricker issue, given that you only
> know the length when the whole object has been retreived. But if the
> object is stored in canonical form then it should be quite easy (file
> size - headers).

Well, the http code handling reading from the upstream socket calculates
this (now) on the fly. I'm hesitant to use file size - headers, because
that _will_ conflict with partial range storage down the track. I was
thinking that adding it to the swap.state metadata would be a workaround
- but how much ram overhead will that entail - (I wasn't planning to
tackle updatable store object metadata just yet :-])...

Rob
Received on Sun Jan 28 2001 - 15:10:46 MST