QUOTE(Natsumer @ Oct 25 2006, 06:43 PM)
Hi Paul,
For answer to Q1, I am baffled. Why does the PDA client need to send a heartbeat signal to the server for push mail to work for Microsoft Direct Push? Is this the case for RIM's implementation as well? Shouldn't there be a mechanism where my cellphone number is co-related with my exchange server email address. So that when the server end detects a mail coming into my mail box, it will establish a data connection (GPRS/UMTS) to my PDA using my cell number, sends the mail across using my email address and my PDA will terminate the call after receiving it. And when I reply the email, the reverse would happen? In this case, this will truely be "Push" mail. Right now, Microsoft Direct Push appears to be Pseudo-Pushmail.
For answer to Q2, it's not the connection charges I am concerned about. I am more concerned about the battery life of my device. With GPRS/UMTS turned on perpetually, my Dopod 838Pro can barely last half a day. It will not do any good at all. I will end up having the capability to check mail on the move but without the actual possibility of staying away for long without a power source!
For answer to Q3, my System Admin use to enable the "Enforce password on device" option. Since then, he has disabled it. But my device is still password locked. Anyways for me to disable this password lock? Thanks.
Sigh... What a trouble to do Push Mail on Microsoft. It's totally half baked!!!

H there,
For Q1, basically, your WM 5.0 (With MSFP) pocket pc connects to your exchange through port 80 or 443 (HTTP or HTTPS, depending on whether encryption option is selected). By making use of fully standard TCP/IP services, it allows Microsoft push mail (or Direct Push) to work regardless of telco firewall settings if any. i.e. It will work even if the telco doesn't give you a public IP as it is the device that initiates the connection. Also, it also means that you do not need to be on a 'blackberry' enabled network to enjoy push mail. Any telco who can give you a standard gprs/edge/3g network will work fine.
RIM's implementation, on the other hand, requires that the telco provision for the service. This is due to the non tcp/ip signalling to achieve the same heartbeat effect. Hence, it is possible for you to visit a country and not be able to have blackberry service. Think about it; occasionally you might have read about RIM announcing 'Blackberry partners with so-and-so telco to bring the blackberry to so and so country'.
Admittedly, with the popularity of the Blackberry, it is unlikely that you end up in a country with gprs telco providers, but no Blackberry. However, the fact remains in that it is entirely possible.
Also, with certain providers like Starhub, you mighit notice that for their non-unlimited data plan; the plain gprs service is actually cheaper than the blackberry one by a significant margin. This is the blackberry licensing at work here as an appropriate server needs to be run to give you the service. There is no such issue with Direct Push.
For Q2, my possible recommendation is that you can try purchasing a 2nd battery... I personally have no such problem, but maybe its because I don't use my PDA phone as a primary source of calls (I carry another phone for voice).
Q3 ah... try to 'delete' the exchange server and 'add' it again. That might resolve it. Do this when connected via usb cable to your desktop/laptop. Your Internet connectivity will be utilized by default instead of gprs data... :)
I personally consider Direct Push to be more elegant and technically superior to the Blackberry's implementation. But I do feel too that the overal 'experience' is still not comparable to the Blackberry. I say it from a position of having used both Blackberry and Direct Push for about a heavy half a year (real life) usage of each.
Regards,
Paul Mah.