|
From: Blat F. <pet...@ho...> - 2000-08-01 17:50:56
|
>From: "Benjamin M. Brewer" <br...@kr...>
>To: Blat Froop <pet...@ho...>
>CC: blo...@li...
>Subject: Re: [Blocks-development] Authenticaion, Ratings, WoT
>Date: Tue, 1 Aug 2000 13:49:32 -0400 (EDT)
>
>
>
>On Tue, 1 Aug 2000, Blat Froop wrote:
> > Remember Blocks currently has a hardcoded filename limit of ~85
>characters.
>
>Why? Is this for any specific reason, or just coded that way?
The 'block' size os hardcoded to 64Kb like this...
typedef struct _block_struct
{
unsigned char block_type; // 'D' => data, 'H' => header unsigned
char send_route[10];
unsigned char return_route[10];
unsigned char text[87]; // <==== filename
unsigned char size[4]; // bigendian uint32 => num bytes in file
unsigned char key[16]; // key to decrypt data blocks
union _payload
{
unsigned char data[65408];
unsigned char block_ids[4088][16];
} payload;
} BLOCK;
Bigger filenames mean less data block IDs in the header blocks
playload... every eatr 16 bytes of filenames reduces the maximum
filesize by 64Kb.
A better design would probably involve having possibly multiple
header blocks allowing files of unlimited size. I have no plans
to change this right now tho.
>
> > Also, you want me to display the hash in the serach window... do
> > you want to see the full thing?... 32 chars is quite long for
> > human readers (and makes the listbox pretty wide).
>
>I'm thinking that once a user 'highlights' (clicks on...) one of the files
>in the search window, the hash value should be displayed in its own little
>'hashbox'.
or in the title bar or somewhere reasonably inconspicuous. If I used
a textbox it would be swipeable which is probably desirable :)
ttfn
PG.
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
|