I think what he means is that if a recorder creates a file and sends it, then corrects it and sends again, the recipient could open the first one and think it is the most current version when it isn't. It wasn't identified as an issue by Peyton but I could see how it could cause someone an issue. My response to that would be to not mail the PDF as an attachment but rather email a link to the user. The link would either lead to a real PDF, stored on disk, or to a CFM file that generates the PDF when it is requested. That would get rid of any caching issue as the file requested is always the latest version. On Sat, Nov 8, 2008 at 6:19 PM, Dean H. Saxe <[EMAIL PROTECTED]>wrote:
> What "things" get asynchronous? If what you say is true, email would > regularly go out without complete attachments. I think you're way off on > this one. > -- Howard Fore, [EMAIL PROTECTED] "The universe tends toward maximum irony. Don't push it." - Jeff Atwood ------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
