I have seen whiteout mail just spinning forever when retrieving mails and opening some mails. I think making it multithreaded may also help. Even on a broadband connection whiteout mail chrome app was not at all usable, it will never complete downloading mails, the notfications can't be stopped, opening single mails can't work. Finally went back to thunderbird+enigmail even though we wanted local password encryption because whiteout did not work at all.
Q: Are the mosh principles relevant to other network applications?
We think so. The design principles that Mosh stands for are conservative: warning the user if the state being displayed is out of date, serializing and checkpointing all transactions so that if there are no warnings, the user knows every prior transaction has succeeded, and handling expected events (like roaming from one WiFi network to another) gracefully.
Those don't seem too controversial, but fancy apps like Gmail-in-Chromium or on Android still behave atrociously on dodgy connections or after switching IP addresses. (Have you ever had Gmail leave an e-mail message in "Sending..." for ten hours while merrily retrieving new mail and not indicating any kind of error? Us too.) We think there may be considerable room for improvement in many network user interfaces from the application of these values.
I have seen whiteout mail just spinning forever when retrieving mails and opening some mails. I think making it multithreaded may also help. Even on a broadband connection whiteout mail chrome app was not at all usable, it will never complete downloading mails, the notfications can't be stopped, opening single mails can't work. Finally went back to thunderbird+enigmail even though we wanted local password encryption because whiteout did not work at all.
Q: Are the mosh principles relevant to other network applications?