A.L.E.C wrote: > Thomas Bruederli wrote: >> And what if people open a message to read, click back to list mode and >> select the next message? Then we doubled the requests to the server >> again. > > Then will be as is now. We can't eliminate every issue, but we could > improve performance of moving between messages (with arrow buttons). > When you double click message on the list you switch to (let's say) > preview mode and now you can move between messages with arrows. Those > moves are causing excessive (in my opinion) getunread calls. > I understand but I suggest to postpone this issue. One goal of the further development of RoundCube is to use more ajax-stuff to dynamically load components that are currently needed. Initially meant to define the plugin-API, we have a draft written by Brennan Stehling for the client-server communication and how the UI is divided into modules that can individually be filled with content. Making use of this, we could get rid of the full-page-loads as we have them right now and maybe even introduce a tabbed UI and this would certainly solve your issue.
But for now, we have to concentrate on cleaning up the code and then implementing the plugin-API. For further reading, see http://trac.roundcube.net/wiki/RoundCube_vNext _______________________________________________ List info: http://lists.roundcube.net/dev/
