> Correct me if I'm wrong, but it sounds like the original source of the
> message is encoded, so you have to decode each message before you can search
> through it?
I believe that this is true.
> If it's faster to do a straight comparison, couldn't you just encode the
> search text and search for that?
One minor problem. In what do you encode the search string?
The stored message can be encoded in many, many different formats. Start
with plain text, add HTML text, various forms of quoted-printable text,
potentially various rich text formats, foreign language text encodings, then
Unicode, and then still other two byte character sets...
In short, there's not a single entity into which you can encode and search.
Which is why you really need to index to do it right. (1)
Life was so much easier as a developer in the days of nothing but plain
text, 7-bit, US-ASCII, messages. ;-)
mikel
(1) Although I note that doing it wrong will work perfectly fine for 75+% of
US-based users. Most of whom will be limited to plain text and HTML text
messages.
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
