Bill la Forge <b.laforge@jxml.com> wrote:
>> Not to mention the ability for the sender to update messages after they've
>> been sent. How many times have you wanted "unsend" a message? Can't with
>> SMTP, but if we just emailed URLs back and forth, you could update the
>> content at the URL before the person you sent it to has downloaded it. This
>> is, of course, both a benefit and a drawback.
> This also solves the problem folk have with email attachments. Too many folk
> continually resend document updates as attachments. This provides an automatic
> system--like a web page, but with a PUSH.
Yes, this is also related to the Eudora Sharing Protocol (ESP), which uses
SMTP and attachments to keep documents in sync, for those who don't run
servers.
http://db.tidbits.com/getbits.acgi?tbart=06112
Updates to documents could be sent out as normal messages, but point to the
same URL, basically informing the email client that there's new data there
that should be downloaded. This would also allow people to subscribe to web
pages and news feeds (like RSS) and have them download for off-line viewing.
But they'd always receive the latest version and would be instantly notified
when something was updated.
--
Aaron Swartz |"This information is top security.
<http://swartzfam.com/aaron/>| When you have read it, destroy yourself."
<http://www.theinfo.org/> | - Marshall McLuhan