Hello,
Usually deleting or moving more than 1500-2000 messages results in a red Server error timeout, so people do it in smaller chunks-- also it can result in duplicates on moves in both the source & dest if a timeout occurs-- I know I could hunt around for timeout increases, but I think those should stay normal, for when a real timeout should happen. Can we start thinking/designing a way to intelligently increase the timeout as needed during long operations... & show a message (like google gmail) it will say: Loading... then Still Loading... Deleting... Still Deleteing... etc. Thanks!!
_______________________________________________ List info: http://lists.roundcube.net/dev/ BT/8f4f07cd
