Confirmed users
360
edits
Mobile/Projects/PushImapProxy: Difference between revisions
Jump to navigation
Jump to search
→Concerns
(→Server: Capitalize IMAP) |
|||
| Line 58: | Line 58: | ||
* There are limits to the number of outbound socket port connections per machine. Can we do rapid polling on servers to reduce our machine cost? | * There are limits to the number of outbound socket port connections per machine. Can we do rapid polling on servers to reduce our machine cost? | ||
** ''asuth'': No. That implies you are keeping the credentials around, and per my discussion with dougt, credentials would be dropped immediately. Also, the "accepted" model for costs is that opening folders is expensive. In practice, it may not be quite as real, but modern servers that support IDLE tend to have a fairly optimized implementation that is very likely to be much preferred over pounding the server. (Accepted in this case is probably unreasonably biased towards sucky implementations like UW-IMAP.) | |||
** Will we need to be whitelisted by major IMAP providers since we may be hitting their machines thousands of times per second from a small number of IPs? | ** Will we need to be whitelisted by major IMAP providers since we may be hitting their machines thousands of times per second from a small number of IPs? | ||
** Some email providers (e.g. Yahoo) only allow third party IMAP/POP access for pay only accounts. There may not be a lot of incentive for them to increase service costs to handle this feature. | ** Some email providers (e.g. Yahoo) only allow third party IMAP/POP access for pay only accounts. There may not be a lot of incentive for them to increase service costs to handle this feature. | ||
*** ''asuth'': Can you clarify? Yahoo has opened up IMAP to pay users, at least for mobile devices, but they don't implement IDLE, so such a service wouldn't work for them anyways. | |||