I feel the messages file should contain exactly what came down the wire.
This is currently not exactly so - as Lex mentioned, the files are
written as text, so if you're using CrLfFileStream, you'll get slightly
different contents. I've been bitten - currently have an old CrLfed
message file I need to convert at some point to my current messages
file.

Anyone have some handy code snippet to do this?

"What came down the wire" is a very stable abstraction that's not too
expensive to convert from - I suggest we stick to it (and maybe make it
CrLfFileStream immune). Also, this is easiest to convert from - I don't
like putting up barriers to exit for users that want to switch away - I
hate it enough when other SW producers do it to me as a user...

This doesn't apply to the index file - an optimization should be fast,
and a search should get appropriate results - I like your solution,
Mike.

Daniel

Mike Rutenberg <mdrs at akasta.com> wrote:
> Lex,
> My approach in this change set was to try to keep things as simple as
> possible, while not touching the messages file data at all.
> 
> What is stored in the messages file is exactly what came across the
> wire.  That means that each time it is displayed, it is converted using
> isoToSqueak (though this is not very expensive).
> 
> What is stored in the index file is (if needed) MIME decoded and then
> converted using isoToSqueak.  That means you can filter for a subject
> field containing "joe", whether it was originally in plain text or was
> MIME encoded.  Previously MIME headers were effectively unfilterable.
> 
> Mike