You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe it is not impossible. RC connects to IMAP server on every request to the HTTP server. When the response is served, IMAP connection is gone. If you need to reduce stress on the IMAP server, use tools like imap proxy or nginx.
The big advantage of IMAP IDLE is that if a change to the mailbox is made (new mail, changes of flags by another client), the client is notified almost instantly. It acts like push mail.
Reducing stress on the IMAP server is a nice side effect. BTW, I already use up-imapproxy.
HTTP in general works in the way that IMAP IDLE is impossible to implement if server do not have some dedicated stateful/persistent service (persistent IMAP/database connections can easily be done with for example jsp (tomcat etc.)).
Currently (and not in foreseeable future) PHP just do not offer any methodology to have persistent connections (let that be IMAP, database etc.) for HTTP services. Command line PHP is different thing.
I think this ticket is invalid for roundcube, however already suggested nginx/imap proxy solves at least part of problem.
I understand your point and agree. Even if we could have IMAP IDLE between RC and the IMAP server, the user would not benefit, since HTTP itself is stateless.
Some admin should close this ticket with "invalid"
I understand your point and agree. Even if we could have IMAP IDLE between RC and the IMAP server, the user would not benefit, since HTTP itself is stateless.
Some admin should close this ticket with "invalid"
I wouldn't say so. It is clearly a difficult task, but using AJAX and a client timeout it certainly would be doable. Likely a feature for roundcube 2.0 or so.
I understand your point and agree. Even if we could have IMAP IDLE between RC and the IMAP server, the user would not benefit, since HTTP itself is stateless.
Some admin should close this ticket with "invalid"
I wouldn't say so. It is clearly a difficult task, but using AJAX and a client timeout it certainly would be doable. Likely a feature for roundcube 2.0 or so.
Hi now there is WebSocket which have less overhead (only 2 byte) compared to AJAX setInterval/setTimeout or longpolling approach
Activity
rcubetrac commentedon Oct 1, 2008
Comment by tensor on 1 Oct 2008 00:08 UTC
I believe it is not impossible. RC connects to IMAP server on every request to the HTTP server. When the response is served, IMAP connection is gone. If you need to reduce stress on the IMAP server, use tools like imap proxy or nginx.
rcubetrac commentedon Oct 1, 2008
Severity changed by tensor on 1 Oct 2008 00:08 UTC
normal => minor
rcubetrac commentedon Oct 1, 2008
Comment by ex sqm on 1 Oct 2008 07:08 UTC
The big advantage of IMAP IDLE is that if a change to the mailbox is made (new mail, changes of flags by another client), the client is notified almost instantly. It acts like push mail.
Reducing stress on the IMAP server is a nice side effect. BTW, I already use up-imapproxy.
rcubetrac commentedon Oct 23, 2009
Comment by joku on 23 Oct 2009 19:32 UTC
Uh.
HTTP in general works in the way that IMAP IDLE is impossible to implement if server do not have some dedicated stateful/persistent service (persistent IMAP/database connections can easily be done with for example jsp (tomcat etc.)).
Currently (and not in foreseeable future) PHP just do not offer any methodology to have persistent connections (let that be IMAP, database etc.) for HTTP services. Command line PHP is different thing.
I think this ticket is invalid for roundcube, however already suggested nginx/imap proxy solves at least part of problem.
rcubetrac commentedon Oct 23, 2009
Comment by ex sqm on 23 Oct 2009 19:56 UTC
Joku,
I understand your point and agree. Even if we could have IMAP IDLE between RC and the IMAP server, the user would not benefit, since HTTP itself is stateless.
Some admin should close this ticket with "invalid"
rcubetrac commentedon Nov 9, 2009
Comment by egallego on 9 Nov 2009 22:59 UTC
Replying to ex_sqm:
I wouldn't say so. It is clearly a difficult task, but using AJAX and a client timeout it certainly would be doable. Likely a feature for roundcube 2.0 or so.
rcubetrac commentedon Mar 17, 2013
Comment by @alecpl on 17 Mar 2013 10:39 UTC
AJAX will not solve lack of persistent connection. I think there's no chance we'll ever implement this.
rcubetrac commentedon Mar 17, 2013
Status changed by @alecpl on 17 Mar 2013 10:39 UTC
new => closed
rcubetrac commentedon Sep 7, 2014
Comment by dhaowoods on 7 Sep 2014 12:48 UTC
Replying to egallego:
Hi now there is WebSocket which have less overhead (only 2 byte) compared to AJAX setInterval/setTimeout or longpolling approach
rcubetrac commentedon Dec 10, 2015
Comment by lkraav on 10 Dec 2015 02:14 UTC
CC-ing. Yes, !WebSocket protocol can definitely be the answer here.