Looking at email from the angle of the wave client being the focus, rather than the mail client...
The way we handle mail is to provide a wave server to mail server gateway that periodically reads mail into the wave client (via the wave server). The wave client presents the mail 'inbox' to the user (so that they may junk spam), and then converts a mail message into a wavelet; first checking if the mail is a reply to a previous message (i.e., the wave already exists), or if this is the first message of a new wave. The approach for that checking involves: Checking the mail sender against the user's contacts database, checking the sender against other users' contacts, checking the sender against previous waves, checking the mail subject against previous waves, checking the sender's domain against a company database (that is able to map users to domain names). When the user replies to the wavelet, the wavelet is saved in the wave (as normal) but the reply is sent out (via the mail gateway) as a mail message... until the sender can be persuaded of the advantages of communication via a wave client of their own :) It's not perfect but it keeps the user in the wave client rather than alt-tabbing back-and-forth to the mail client. For POP3 it has the huge advantage of storing mail within an integrated database rather than in individual user inboxes. This leads on to the ability to directly integrate mail messages with other aspects of the user's business transactions (which are also integrated into the wave client - such as orders, fulfillment, settlement, and accounts). HTH Chris -- iotawave.org -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
