On Tue, 4 Mar 2003 16:55:38 +0200 Timo Sirainen <[EMAIL PROTECTED]> wrote:

> That's what I meant with "fetching BODY", except I remembered BODY was
> enough. But still, fetching BODYSTRUCTURE is pretty much useless
> cpu/bandwidth usage just for one paperclip icon.

No, it's not.

A well written client should fetch BODYSTRUCTURE as preferentially before 
fetching any other body data.   The amount of bandwidth used in the 
fetch, with the possible exception of handheld devices (which are 
exceedingly unlikely to be able to display attachment data anyway), is 
simply a non-issue.   For the vast majority of mail clients in use it is 
round trips that kill -- latency, not bandwidth.

Fetching the bodystructure provides you will the ability to do proper 
MHTML processing, security processing, and body structure presentation.   
All the things that you want to do in a good client.

Sucking down the entire RFC822 text to get at the message structure -- now
that's a waste of bandwidth, processing power and time for messages that 
may never be looked at.

Cheers.

---
Steve Hole
Chief Technology Officer - Billing and Payment Systems
ACI Worldwide
<mailto:[EMAIL PROTECTED]>
Phone: 780-424-4922

Reply via email to