Exchange Activesync的推送机制
我对推送电子邮件的整体设计有疑问，特别是 Exchange ActiveSync 所采用的方法。
据我了解，有两种基本方法可以通过以下架构获取推送电子邮件
设备<--->推送电子邮件服务器<--->实际电子邮件服务器
- 在推送电子邮件服务器和设备之间保持恒定的套接字连接。推送电子邮件服务器将通过连接通知设备。
- 相关技术 - IMAP IDLE
- 无需短信网关
- 电子邮件服务器将发送消息（wap 推送、短信等）要求设备下载新电子邮件。
- 相关技术- OMA-ENM
- 推送电子邮件服务器需要 SMS 网关
考虑到这一点，Exchange Activesync 实际上提供什么类型的推送电子邮件服务？
（据我所知，Emoze/Synchronica 的白标签推送解决方案使用第一种方法 - 通过 IMAP-IDLE 等方式持续连接）。
I've a question regarding the over all design of push email and specifically the approach taken by Exchange ActiveSync.
As I understand there are two basic ways to get push email with the following architecture
Device <---> Push Email Server <---> Actual Email server
- Keep a constant socket connection between Push email server and device. Push email server will inform device over the connection.
- Related technology - IMAP IDLE
- No sms gateway required
- The Push email server will send a message (wap push, sms etc) to ask device to download new email.
- Related technology- OMA-ENM
- Needs a SMS gateway at Push email server
Considering this, what type of push email service does Exchange Activesync actually offer?
(AFAIK, white label push solution from Emoze/Synchronica uses the 1st approach - constant connection over something like IMAP-IDLE).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Exchange ActiveSync 使用直接推送。客户端（电话等）与 Exchange 服务器同步，然后发出一个长时间运行的 HTTP POST 请求（称为“PING”，但它不是 ICMP ping 或类似的东西）。当客户端发出请求时，他们指定它应该运行多长时间（通常是几分钟）。
该 HTTP POST 请求将在 Exchange 服务器端闲置，直到邮箱发生更改或客户端请求的时间段过去而没有发生任何有趣的事情。
在前一种情况下——邮箱中发生了某些变化——POST 调用的返回值向客户端表明它需要与邮箱重新同步以获取最新的更改。
在后者的情况下 - 根本没有任何变化 - 返回值指定了这一点，并且客户端只需将另一个长时间运行的 PING 重新发送到服务器，再次重复整个过程。
所以这是你的第一，真的。有关详细信息，请访问此 Microsoft 链接，了解更多详细信息。
Exchange ActiveSync uses Direct Push. The client (phone, whatever) syncs with the Exchange server and then makes a very long-running HTTP POST request (called a "PING", but it's not an ICMP ping or anything like that). When the client issues the request they specify how long it should run for (typically it's on the order of many minutes).
That HTTP POST request will sit there idle on the Exchange server's side until either a change occurs in the mailbox or the time period requested by the client had simply passed with nothing of interest happening.
In the case of the former - where something changed in the mailbox - the return value of the POST call indicates to the client that it needs to re-sync with the mailbox to pull down the latest changes.
In the case of the latter - where nothing changed at all - the return value specifies this and the client simply re-sends another long-running PING to the server, repeating the whole process again.
So it's your #1, really. For more information, this Microsoft link goes into more detail.
我认为 Exchange ActiveSync 提供了类似于 IMAP-IDLE 的功能，请参见下文...
http: //technet.microsoft.com/en-us/library/aa997252.aspx
如果您得出不同的结论，请发布。谢谢！
I think Exchange ActiveSync offers something similar to IMAP-IDLE, see below...
http://technet.microsoft.com/en-us/library/aa997252.aspx
If you've come to a different conclusion please post. Thanks!