Thread: Mail for Exchange (MfE). Blame me here, pls
View Single Post
vitaly_repin's Avatar
vitaly_repin is offline vitaly_repin
2009-11-28 , 12:51
Posts: 320 | Thanked: 763 times | Joined on Oct 2009 @ Espoo, FInland
#137
Originally Posted by dneary View Post
First - is the MfE module source code public?
No. I would be more than happy to make it public. And (as a sw. engineer, not as Nokia employee!!!) I think it could be (legally and technically) possible for Exchange 2007 part. Not for Exchange 2003. The difference is that Exchange 2003 ActiveSync protocol specs are not public.

But the problem is that I need to explain to my management what will be the benefit of making it open-source. And you most probably know that Nokia and MS are partners in certain areas and the decision to open-source this component can not be simple.

Is there any way that the community could address any problems with the Google interaction?
To make this fact visible to the decision makers in Nokia and Google. And the community is doing it quite well in this thread, I have to admit

I and other team members want to make it compatible with Google (obviously) but I can not keep it as a personal (or even several individual's) activity. Besides all, it contradicts with my life principles - be transparent and never hide work-related activities from the management.

Second - do you have a test suite for MfE, with details on the stuff which definitely/sometimes doesn't work with Google (calendar, contacts or mail), please?
We do. But they are not public. I can say here that the typical problems with google now are timeouts. Server processes our requests much longer than (really heavy loaded) Exchange 2007 server.

Besides this, the problems which regular users are experiencing with google now have the same root cause as the problems of Exchange 2003 users. But delivering Exchange 2003 support does not mean automatic bringing of google support on board. In order to support the new implementation of the protocol (google implementation in this case), we have to make interoperability tests. Full set of them. Otherwise, it will be again "if it works for you, you are lucky". The percentage of the lucky people will increase, but it will not solve the real problem.

Third - Do you know if there is a way to synchronise contacts over SyncML with Google? This worked pretty well for me on my Nokia N82, I imagine (?) that it might also work well with my N900, if the client software's been ported.
Have no idea about this. To port the software from N82 to N900 is not a trivial case as the operation systems are different. N82 is Symbian-based while N900 is linux-based.

But if there is a software for previous maemo editions which addresses the same use case, the porting will be much easier.

- I have regular failed syncs with contacts.
- On at least one occasion, a sync which failed half way through left me with only a third of my contacts on the phone. A successful sync afterwards got me back into a better position.
Timeout issue I have mentioned above. It (most probably) failed because of timeout. The next sync started later and completed the previous sync task.

- It may only be an impression, or an interaction of a wifi issue & the sync issue, but I have the impression that often, after failed syncs, I lose routing information for my wifi connection too. I stay connected to my access point, but there's no DNS resolution or external internet access.
The probability that sync and this problem are related is close to zero as MfE does not do anything with connection management except requesting the internet connection when there is no connectivity in the device.

Anyway, thanks for MfE, and even if it doesn't work yet, it seems to me like there is a desire to go this route for Google and Nokia, so I imagine it will work better as time goes on.
Thank you for your time and feedback you have given.
 

The Following 15 Users Say Thank You to vitaly_repin For This Useful Post: