Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update TIdIMAP4 to support the IDLE command #147

Open
rlebeau opened this issue Apr 6, 2017 · 0 comments

Comments

@rlebeau
Copy link
Member

commented Apr 6, 2017

The IDLE command (http://www.ietf.org/rfc/rfc2177.txt) allows the server to push real-time message notifications to the client, instead of having the client poll the server for changes periodically. However, TIdIMAP4's current blocking command/response code model cannot support that as-is. The IMAP protocol is not a clean command/response model like other common Internet protocols. It can have unsolicited data inter-mixed between commands and their responses. At the very least, in order to support the IDLE command, TIdIMAP4 would need to run an internal reading thread during the time that the IDLE state is active, and not allow any outbound commands to be sent until the IDLE state is deactivated.

@rlebeau rlebeau added this to the Indy 12 milestone Apr 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.