Re: [Jmap] Best vs Good enough - adoption of JMAP

[Ned Freed <[e-mail]>]

> On Apr 26, 2017, at 9:45 AM, Ned Freed <[e-mail]> wrote:
> > Now take these semantics and multiply them by the number of users you have,
> > which can be in the many millions. And while sometimes you can treat
> > this as single, system-wide queue for monitoring purposes, sometimes
> > you'll need to lookup and probably monitor on a per-user basis.

> Of course, when the user calls in with a problem with their email, the fact
> that all the information about that user's email is in their unique mail store
> is kind of convenient.

Actually, it offers no utility whatsoever. If you provide the ability to answer
such queries at high scale, you do it based on trasactional information
produced by the message transport infrastructure. This information is fed into
some kind of database that lets you lookup whatever you want for whatever
combination of sender, recipient, time window, etc. you want to support.

You most certainly don't want to do it by accessing the mailstores. They
carry enough load as it is; using them to handle a problem that's easily
separable makes no sense.

There's also a nontrivial security separation concern here. The access rights
associated with being able to look at transaction data are not the same as the
rights needed to look at message content.

				Ned