I think this discussion should move to dbmail-dev. I've already finished most of the singleton mimechunk storage :-)
A bit raw around the edges, and only for sqlite atm. Stay tuned. Fully backward compatible: just add two tables like I stated. Using sha1 over the whole of the file, fall back to old-style storage if new-style not available. I guess the one doing the work gets to make the decisions... In this new setup; simple rfc2822 messages are stored in a single block. Yes: no more chopping off of the headers. For multi-part messages, the first block contains the rfc headers plus the mime-preamble. Following blocks contain the mime-parts as-is. Boundaries between parts are reconstructed at retrieval based on the boundary used in the original message and stored in the first block. I'm using the sha1 code from the mozilla project (dual licence). It's what Linus uses in the GIT code, so it *must* be fast. Are we having fun yet? -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
