WM 5.0: POOM and CeSet/GetReplChangeBitsEx

[Frank]

In the WM 5.0 release, the bit replication functions do not work with
POOM oids.

* CeSetReplChangeBitsEx
* CeGetReplChangeBitsEx
* CeClearReplChangeBitsEx

http://blogs.msdn.com/ce_base/archive/category/10306.aspx

Does anyone know if Microsoft is planning on making these function
calls work with the POOM oids? And if so, when?

I'm debating whether to code the workaround or just wait for the
Microsoft fix.

 

[John Socha-Leialoha]

The repl bit calls you've listed below aren't in any of the header files
on my machine. I seem to remember hearing that they're part of platform
builder. The idea, as I was told, is that this access is designed for
use by OEMs, not by ISVs. So much that I wanted to use them for PPC
2003, I found other ways around the problem.

My experience with Microsoft on this issue is that they don't really
understand that third party developers have a need to create their own
synchronization solution. They seem to be of the opinion that ActiveSync
will be the only synchronization people will ever need. As a result,
they see no reason to expose functionality that would allow anyone else
to easily build a synchronization engine.

In other words, code around.

-- John

 

[WebIS]

http://blogs.msdn.com/ce_base/archive/2005/09/23/473300.aspx