I know this topic has been debated to death but I had two questions that I was hoping people could help me with :) Our management are toying with the idea of replacing BES with ActiveSync going forward.
From reading up on the Internet, the three major benefits of BES over EAS are:
1. Push/Pull: Reading here
"Mobile devices that support Direct Push issue an HTTPS request to the Exchange server that asks Exchange Server to report any new or changed e-mail messages, calendar, contact, and task items. If changes occur within the lifespan of the HTTPS request, the Exchange server issues a response to the device that includes which folders have new or changed items. The device then issues a synchronization request to the server. After synchronization is complete, a new HTTPS request is generated to re-start the process."
To me, this isn't real Push technology! Basically, the EAS client is 'checking in' with Exchange regularly to see if it has new mail.
Would I be correct in saying that if BES knows there is a new message for a user (via the UDP notification), then it sends the message directly. The handheld doesn't actually need to keep checking in with BES?
That said, does this make much of a difference given that most people are on unlimited data plans now?
BES uses 3DES which is 'virtually unbreakable'. EAS uses HTTPS. Isn't HTTPS virtually unbreakable too though?
I think everyone agrees BES has loads more IT policies though.
3. Data compression
BES's compression of data is much more effecient than EAS's. But - again - what effect does this have on the user given the unlimited data plans?
BES logs, when used with BRK, are great are pinpointing issues. EAS IIS logs is very much 'needle in a haystack' situation.
I'm interested in both BES and EAS viewpoints!