> Aren't Apple's "v-twin" (or whatever they came o be called) APIs available?
> I vaguely remember that any app could make use of the facility...(very
> vaguely) And if Cyberdog was an example, it was brilliant.
The DDK for the "Apple Information Access Toolkit"
<ftp://ftp.apple.com/developer/Development_Kits/AIAT_1.1.sit.hqx >
seems to incorporate a goodly bit of this functionality. Although I note
that the DDK is 2 1/2 years old. And, so far as I know, hardly anyone has
adopted it.
At first glance, there's a goodly amount of work necessary to get from there
to what's required for an email client.
For what it's worth, long ago, when we were wrestling with this problem, we
decided that in the day and age of people sending annoying 1+ megabyte
binary attachments, that it was perfectly reasonable to conceptually store
both the original version and a pre-parsed version of an incoming textual
message.
So long as you only do this for the various text types that aren't "real
encodings" (eg base64, uuencode, hqx), you really don't store that much
extra data. Two to three years ago, when we were looking at the problem, it
really only pushed the storage requirements by a trivial amount for a
typical user.
mikel
PS: Actually, in the interest of honesty, our final implementation only
stored the decoded MIME parts and reconstructed the originals from that.
But *I* still prefer the concept of storing both.
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
