Re: [Imap-protocol] If Crispin were creating IMAP today how would it be different?
Ladar Levison <[email protected]> Wed, 11 Mar 2015 11:39:00 -0500
| Newsgroups | gmane.mail.imap.general |
|---|---|
| Message-ID | <[email protected]> |
On 3/11/2015 11:24 AM, Bill Janssen wrote: > I did say, "for instance". A number of different database systems > support replication, but replication for mobile is a harder problem. Very true. As I recall Microsoft also has a DB replication/sync framework that is supposed to work well over unreliable/slow network links. I've never put their claims to the test though. https://msdn.microsoft.com/en-us/sync/bb736753.aspx > I should admit: we're experimenting with new email MUA. I wrote the > MDA to support it, and designed a custom (non-IMAP) MUA/MDA protocol to > support unique features of the MUA -- and it doesn't use database > replication. Link? Or you keeping this piece of brilliance all to yourself? I'm still looking for inspiration on my protocol design effort. I know how to handle most of the functionality, but I'm still wrestling with how to sync an encrypted binary file back to the server in a way that is safe, and not overly complex... So when I hear "replication" I start to think you may have the answer I'm looking for. Of course before I worry about that problem I still need to decide which scheme I'm going with. Lately I've been leaning towards sticking with a line based protocol, aka, IMAP, but having it to send/receive JSON objects... _______________________________________________ Imap-protocol mailing list [email protected] http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVAG+kAAoJEMR5kTl8dRp/xOQQAK/yZPuNjis/poyadWKG3xOZ XhQNMkQMaDDKfLbLkUo1aGudoW4/e8feH/DRRp8xHKRVs8+t0jpEORInk664n2bc lC3c7BBarvg4CTYsxNSEEUBRWrC6O1PdA35aV2bUBlbFv8zuWN0YMdknwV9raSQP Sy8GRn9c8ZkGUg+uqdC5kzwfSM+nStYvOuHXUrWq2/SLeolsA4lkSObgtp0DQoi9 Lt7k/W47ZAfk654bk6+kZFcY+6hEiHJhKtVjWsmIrOCyU00KInAf/XJKrIZC44rV PtPiuGbpF+1sUl/IIttWCngHPa8oBXC3Z4ATFHUizItKRDTf3lYgaq/iAMMGOfzd DhzedefxFnCa1yoDxuwSyBh82VwRXLNT/inHPwSUGt9dXe5xCy5W1OmJCQLpQZJK 0XwGLYV/g6M2X3eGGMZPQMpRnxpukR8brVYZBXv+1junejzxzlfENjgCzuGevYOT Sg3h5VRuAc8K6HbYpBqOZiwBsHFJ7hejb3T/t1bCyO+XtYcbacmOkMeMrX+S3Z91 d5VTEuzKSb8UGhUioYoCKodC4WpoXQF1Whswh1OwcmJTFvD3K3n2FOsWyDvV7zXH pUqY20sFo+im/cgt4cjfNlTcK61spTUvDLyvCXIkqdjerVEhGOHZaJxeMiOzZ06H iGOjyBMCalexLjlKHH3h =VQlL -----END PGP SIGNATURE-----