On Fri, 2009-09-25 at 13:49 +0200, Patrick Ohly wrote:
> > There is also a server config sample in the sysync_SDK/configs
> > subdirectory (that's the one I have used in my tests).
>
> This morning I implemented a rudimentary HTTP server in Python which
> uses the SyncEvolution Connection D-Bus API to pass messages into
> SyncEvolution. I'm still in the process of figuring out how to
> interact
> with the server engine, though.
Ah, progress. In other words, more questions... ;-)
How do I tell the server which URL to use and how to append (or not to
append) the ?sessionID=... suffix? The <serverurl> element is only valid
for clients.
You said that OpenSession() accepts a sessionID created by the app. I
could use that when I want to create my own ID. If I don't do that, can
I query which session ID was generated by the engine?
Profiles are gone in the server. How do I control the sync modes used by
the server for specific datastores? I'm using
<plugin_module>[SDK_textdb]</plugin_module>
<plugin_sessionauth>yes</plugin_sessionauth>
<plugin_deviceadmin>yes</plugin_deviceadmin>
for the server and my own plugin for each datastore.
A related question: I was using the "dbname" in a target to find the
datastore name related to a progress event. The code looked like this
(with wrapper classes around the underlying handles):
SharedKey targets = m_engine.OpenKeyByPath(profile, "targets");
SharedKey target;
target = m_engine.OpenSubkey(targets, progressInfo.targetID);
std::string name = m_engine.GetStrValue(target, "dbname");
Is there a better way that works in both client and server?
At the moment I can start a sync session, but SessionStep() returns an
error at some point. Need to look more closely into that before I can
say more...
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
