On Fr, 2010-02-12 at 17:03 +, Lukas Zeller wrote:
I can just say, if you come to the point where a superdatastore seems
to need any admin data (profiles, maps, anchors, whatever) you're off
track :-)
That's what I expected ;-) I only asked for hints while looking into the
source further. I
On Do, 2010-02-11 at 19:50 +, Patrick Ohly wrote:
[no target for superdatastore]
The only solution I see is to make the subdatastore URI's more complex:
instead of foo, let's use foo:uri where foo is the name of the
superdatastore and uri its remote URI.
I'm going with that and have syncs
Hi Patrick,
I can just say, if you come to the point where a superdatastore seems to need
any admin data (profiles, maps, anchors, whatever) you're off track :-)
So, regarding engPrepareClientSyncAlert(): The problem is that this, as a
client-only routine, has never been made superdatastore
Hi Patrick,
There can't be a a target nor a TBinfileImplDS for the superdatastore.
This still holds true...
You almost had me convinced and I already changed quite a bit of code,
until I came to the point where I wanted to call dsSetClientSyncParams()
for the superdatastore. If that store
On Fr, 2010-02-12 at 17:14 +, Lukas Zeller wrote:
The only solution I see is to make the subdatastore URI's more complex:
instead of foo, let's use foo:uri where foo is the name of the
superdatastore and uri its remote URI.
Makes sense. Just a cosmetic thought: why not foouri, so the
On Do, 2010-02-11 at 17:19 +, Lukas Zeller wrote:
On Feb 11, 2010, at 13:44 , Patrick Ohly wrote:
b) An enhanced SelectProfile() in binfileimplclient.cpp, which would
check that flag and figure out which superdatastore to instantiate in
addition to the normal datastores.
Is that
Hello!
Does the binfile-based SyncML client support superdatastore in its
config? This would be useful for OVI.com, which seems to have issues
when using separate event and todo URIs (as Lukas found out when he
tested it).
I'm trying to use a superdatastore and get a segfault:
// - find target
