Ian Clarke - ian at emu.locut.us wrote:
> On 19 May 2006, at 10:17, Matthew Toseland wrote:
>
>>> On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that compressing anything that has already been compressed, such
On Friday 19 May 2006 18:56, Matthew Toseland wrote:
> Most of the time I expect the node to decide what goes into a
> container. How can it decide this? I propose the following rules:
By all means, include something that lets the user decide about the
packaging.
> Maybe on ClientPutComplexDir,
Ian Clarke - [EMAIL PROTECTED] wrote:
> On 19 May 2006, at 10:17, Matthew Toseland wrote:
>
>>> On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that compressing anything that has already been compressed, such
>>
Ian Clarke wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 19 May 2006, at 10:17, Matthew Toseland wrote:
>
>> On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Note that compressing anything that has alrea
On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Note that compressing anything that has already been compressed, such
> as most image, audio, or video formats, is pointless.
True, but packing them may be far from pointless. Also,
Most of the time I expect the node to decide what goes into a container.
How can it decide this? I propose the following rules:
- Anything which is over 3 blocks compressed (10 blocks uncompressed?)
should not go in a manifest.
- Anything much larger than the average probably shouldn't go in a
On Friday 19 May 2006 18:56, Matthew Toseland wrote:
> Most of the time I expect the node to decide what goes into a
> container. How can it decide this? I propose the following rules:
By all means, include something that lets the user decide about the
packaging.
> Maybe on ClientPutComplexDir,
Ian Clarke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 May 2006, at 10:17, Matthew Toseland wrote:
On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that compressing anything that has already been compressed, such
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 May 2006, at 10:17, Matthew Toseland wrote:
On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that compressing anything that has already been compressed, such
as most image, audio,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 May 2006, at 10:17, Matthew Toseland wrote:
> On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Note that compressing anything that has already been compressed, such
>> as most i
On Fri, May 19, 2006 at 10:10:03AM -0700, Ian Clarke wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Note that compressing anything that has already been compressed, such
> as most image, audio, or video formats, is pointless.
True, but packing them may be far from pointless. Also,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that compressing anything that has already been compressed, such
as most image, audio, or video formats, is pointless.
Ian.
On 19 May 2006, at 09:56, Matthew Toseland wrote:
Most of the time I expect the node to decide what goes into a
co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note that compressing anything that has already been compressed, such
as most image, audio, or video formats, is pointless.
Ian.
On 19 May 2006, at 09:56, Matthew Toseland wrote:
> Most of the time I expect the node to decide what goes into a
>
Most of the time I expect the node to decide what goes into a container.
How can it decide this? I propose the following rules:
- Anything which is over 3 blocks compressed (10 blocks uncompressed?)
should not go in a manifest.
- Anything much larger than the average probably shouldn't go in a
14 matches
Mail list logo
