I've resolved the problem modifying "test_syncevo-http-server". I've added a
routine that prints the output of syncevo-dbus-server in a file placed into
${HOME}/.cache/syncevolution/ . In this way, when a new client tries to
connect to the server, I manage to read the deviceID and to automatize the
routine of registration of a client.2011/1/24 Patrick Ohly <[email protected]> > On Fr, 2011-01-21 at 17:23 +0000, Giuseppe Gerace wrote: > > For the moment, I'm interesting in detecting output. If I'm not wrong, > > your last file "test_syncevo-http-server.py" included either the http > > server or the syncevo-dbus-server. I can also modify > > "syncevo-dbus-server.cpp", but then how I can integrate it with your > > test_syncevo-http-server file? > > When you modify syncevo-dbus-server.cpp, you need to recompile > SyncEvolution to produce a modified "syncevo-dbus-server" executable. > syncevo-http-server communicates with that via D-Bus, so no need to > modify the HTTP server script. > > > I think it's more easy to catch the output, but the first part of a > > client's registration don't generate any html log file, if I'm not > > wrong. You can confirm my hypothesis? > > I think that's right. > > Can you say a bit more about what you are trying to achieve? If this is > about a one-off thing, like getting your own device working, then the > manual approach should be way easier. > > If this is about supporting multiple devices automatically, then it > would make a lot more sense to put it into SyncEvolution properly. > > -- > 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. > > > -- Giuseppe Gerace
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
