Diego Roversi <[EMAIL PROTECTED]> writes:
> Compressed store make sense only if the are readonly or used with a
> "substore" that can shrink or grow at will. That happens because you can't
> know how well data can be compressed. The only way to handle correctly is to
> compress the data at fs lay
On Wed, Jan 16, 2002 at 04:15:22PM +0100, Marcus Brinkmann wrote:
> If you use gunzip:STORE where store is any store, it will create an
> uncompressed copy in memory. STORE can also be the concat store, or ileave
> store or whatever. But note that this is probably not what you want (writes
> ge
On Tue, Jan 15, 2002 at 05:41:41PM -0800, Galchin Vasili wrote:
> 1) In "store.h" type servers, what is the best way for me to
> understand the pager.c file? I.e. is it external storage
> management?
It is external memory management, eg the callbacks required by libpa
Hello,
1) In "store.h" type servers, what is the best way for me to
understand the pager.c file? I.e. is it external storage
management?
2) A brief answer to what is defpager server and where are the
other pieces like main.c?
3) Using kids (children
