Hello Scott!

11 Jun 2010 06:31, Scott Little wrote to Benny Pedersen:

 SL> What I mean is, the Squish format has a chain of message frames and
a chain of free frames.

as in random access database nearly ?, i remember this from my work in
comal 80 on commodore 64, each data record could be deleted seperately and
later data could be added to this record number, i belive this is what you
like squis to do in future, but i am unsure if its can be done sine not
every msg is eg 64k pr frames, or is it just one frame pr msg ?

in c64 db, it was exactly just 254 bytes pr record max

 SL> AFAICT, sqpack does not move deleted messages from the message
chain to the free chain, it repacks the area with just the non-deleted
messages.

this is slow to move anything, its faster to just delete msg num in the
index, but here i dont know if thats what being done in squish api

 SL> So I wanted to know if there's a way to actually make use of the
free frames chain feature.  I can write a replacement for sqpack, but if
HPT won't use 
 SL> free frames either way, there's no point.

well make the code first based on orignal sqpack, then make a diff -urp
originaldir patcheddir > sqpack.patch

post it here :)

or ask devs to help make it into husky


 Regards Benny


... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/2.6.34-gentoo (i686))