I suspect, but do not know for sure, that if rwg did not make additional edits, he would not get "duplicates". It is probably the additional postscripts that make it a new, different message, so gmail won't invoke a duplicate suppression algorithm. Both TCP and SMTP have duplicate message suppression as part of the protocol. On Sep 2, 2012 8:49 AM, "Robert Munafo" <mrob27@gmail.com> wrote:
Yes, you're right, I missed the point.
I think that email clients should tell the (human) sender when the email has been opened by the (human) recipient. The rest of the steps (like sending the email from the browser to one of gmail's servers) are details that are not as important.
I would go in the direction of making the user wait a day or two to find out if his message has been read.
On 9/2/12, Andy Latto <andy.latto@pobox.com> wrote:
And I think that the algorithms you are describing below are the solution to a different problem than the one that Gmail is trying to solve. [...]
-- Robert Munafo -- mrob.com Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com
_______________________________________________ math-fun mailing list math-fun@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/math-fun