On Freitag, 1. Juni 2007 Jake Anderson wrote: > So you are moving to splitting the messages on logical boundries (ie > message bodies, headers,attachments) rather than the 512k blocks? One > would have to think that would help performance on large messages > greatly? especially if you can (optionally?) move the big files out > of the DB
I highly oppose against moving anything out of the DB. After all, we use the DB in order to have the advantages from it: scalability, (high) availability, replication, etc. If there are external files, who copies them to the other servers, etc? As I understood, the 512k junks will stay, it's just they are organized into pieces of attachments, mime-types, etc. There will be a checksum of each file (md5 or so), so that 2 different e-mails can link to the same attachment. Still there can be the problem of checksum collissions, especially on really large DBs, so I'd suggest using two checksum algorithms. Or maybe make an md5 sum over each 512k junk, then apply md5 and sha1 on those checksums only, for a quicker calculation. Under no circumstances it should ever happen that "high secret attachment" of user A has the same checksum of "funny pic" from user B, and the DB makes a link for user B to "high secret attachment" of user A. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: EA39 8918 EDFF 0A68 ACFB 11B7 BA2D 060F 1C6F E6B0 // Keyserver: www.keyserver.net Key-ID: 1C6FE6B0
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
