New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrote the paragraphs on public-key routing, added several projects and improved the overall accuracy of assertions #10

Open
wants to merge 22 commits into
base: master
from
Commits
Jump to file or symbol
Failed to load files and symbols.
+9 −0
Diff settings

Always

Just for now

Viewing a subset of changes. View all

paragraph on scalability of email systems

  • Loading branch information...
carlo von lynX
carlo von lynX committed Apr 25, 2014
commit 0809f6ccd46d6cb7fc4f0e3666c052f74e27471c
View
@@ -8,6 +8,7 @@ Contents:
1. [Forward Secrecy](#forward-secrecy)
1. [Data Availability](#data-availability)
1. [Secure Authentication](#secure-authentication)
1. [Scalability](#scalability)
1. [Web Mail](#web-mail)
1. [Mega](#mega)
1. [PrivateSky](#privatesky)
@@ -97,6 +98,14 @@ For those projects that make use of a service provider, one of the key problems
No consensus or standard has yet emerged, although SRP has been around a while.
<a name="scalability"></a>Scalability
-----------------------------------------------------------
Limitations in scalability are traditionally accepted in e-mail. Should you need to send a message to a mailing list of ten thousands of users, it is accepted that your server will be busy all day doing just that. Should you instead own an account at Google Mail and happen to have a mailing list of a million other Google users, then it is accepted that the message will be distributed in a question of seconds.
This discrepancy is due to the federated architecture of SMTP known not to scale very well while a mail system which is fully internal to a commercial cloud can make use of advanced publish/subscribe distribution trees. Some advanced email replacements also take this aspect in consideration and try to improve on the scalability of email by introducing anonymized distributed publish/subscribe strategies. Frequently they also include the capability of delivering binary encoded data natively, thus reducing in encoding overhead compared to email's MIME formats.
<a name="web-mail"></a>Web Mail
===========================================================
ProTip! Use n and p to navigate between commits in a pull request.