d89ca72d01
When using GIO, it is possible to avoid the DBusServer listening on a publicly accessible address. Connection setup becomes more reliable, too, because the D-Bus server side can detect that a child died because the connection will be closed. When using libdbus, the traditional server/listen and client/connect model is still used. GDBus GIO mimicks the same API to minimize changes in ForkExec. The API gets simplified to support both approaches: - Choosing an address is no longer possible (was only used in the test example anyway) - The new connection callback must be specified already when starting the server. The GDBus GIO implementation uses SyncEvolution utility code. Strictly speaking, this creates a circular dependency libsyncevolution<->libgdbus. This is solved by not linking libgdbus against libsyncevolution and expecting executables to do that instead. The GDBus GIO example no longer linked because of that; it gets removed because it was of little value. Now that we started using CLOEXEC, we might as well use it for the permanent file descriptors created for each ForkExec instance. |
||
|---|---|---|
| .. | ||
| Algorithm | ||
| keys | ||
| test-dbus | ||
| testcases | ||
| __init__.py | ||
| abort-redirect.cpp | ||
| bluetooth-device-id-inspector.py | ||
| client-test-main.cpp | ||
| client.supp | ||
| ClientTest.cpp | ||
| ClientTest.h | ||
| ClientTestAssert.h | ||
| compare.xsl | ||
| COPYING | ||
| cppcheck-wrapper.sh | ||
| dbus-client-server.cpp | ||
| dbus-server-config.py | ||
| dbus-server-connect.py | ||
| dbus-server-http.py | ||
| dbus-server-sync.py | ||
| dbus-session.sh | ||
| evo.supp | ||
| generate-html.xsl | ||
| IcalTest.cpp | ||
| log2html.py | ||
| Makefile | ||
| notification-daemon.py | ||
| proxy.py | ||
| README.funambol | ||
| README.google | ||
| README.googlecalendar | ||
| README.memotoo | ||
| README.mobical | ||
| README.nokia_7210c | ||
| README.Ovi | ||
| README.qtcontacts | ||
| README.scheduleworld | ||
| README.syncevolution-server | ||
| README.yahoo | ||
| README.zyb | ||
| resources.py | ||
| resultchecker.py | ||
| run_src_client_test.sh | ||
| runtests.py | ||
| synccompare.pl | ||
| syncevo-http-server-logging.conf | ||
| syncevo-http-server.py | ||
| syncevo-phone-config.py | ||
| sys.supp | ||
| test-dbus-concurrency.txt | ||
| test-dbus.py | ||
| test.am | ||
| test.cpp | ||
| test.h | ||
| testdbus.py | ||
| valgrindcheck.sh | ||
| wrappercheck.sh | ||
This document is used to show interoperability test information with zyb server.
http://bugzilla.moblin.org/show_bug.cgi?id=2424
* The zyb Server's device information
ZYB HTTP SyncML Server
Version:3.9.18
Build:3.9.18b572
* Test Environment Variables Settings
CLIENT_TEST_SERVER=zyb CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/test/
* Test Profiles Settings
-- N/A
* Data formats we need to test:
-- Client::Sync::vcard21
* Know Limitations in ZYB server:
VCard21
-- Only below properties are accepted:
FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, TZ, GEO, TITLE, ROLE, LOGO, ORG, NOTE, REV, SOUND, URL
-- The property 'N' parser error: treat "\;" as the delimiter
-- The property 'ADR': if it is long, three extra chars '\r', '\n' and ' 'will be added in the property value.
-- Server does escaped text processing, e.g, "<\;" is converted to "<"
-- Server sends mismatch anchors between two sync even if there is no failure.
* Known test failures:
-- NONE