-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
imap_close #59
Comments
No, constantly closing and opening the connection would be a serious drain on resources for both the server and the client (in this case, whatever app is using Fetch). If you look at email clients that live on the desktop they all maintain their connection over the long term. |
Doesn't this library naturally create a new connection across requests though? How does the connection stay persistent against a page reload for example? |
It doesn't. Each page request or run of the application has it's own connection. A change to this application that may make sense is adding imap_close to the Server object's destructor function, but it certainly should not be done after each operation. |
+1 for that |
#62 should take care of this :) |
#69 is the latest version, now that I'm using branches... |
Shouldn't imap_close be called after each operation?
The text was updated successfully, but these errors were encountered: