3c01a1ebf6
This adds GetPeerStatus() and "progress" events. To detect DB changes as they happen, the SyncSource operations are monitored. Upon entry, a counter gets increased and transmitted through to the PIM manager in syncevo-dbus-server using extended SourceProgress structs (only visible internally - public API must not be extended!). This will count operations which fail and count those twice which get resumed, so the counts will be too high occasionally. That is in line with the API definition; because it is not exact, the API only exposes a "modified" flag. Progress is reported based on the "item received" Synthesis event and the total item count. A modified libsynthesis is needed where the SyncML binfile client on the target side of the local sync actually sends the total item count (via NumberOfChanges). This cannot be done yet right at the start of the sync, only the second SyncML message will have it. That is acceptable, because completion is reached very quickly anyway for syncs involving only one message. At the moment, SyncContext::displaySourceProgress() holds back "item received" events until a different event needs to be emitted. Progress reporting might get more fine-grained when adding allowing held back events to be emitted at a fixed rate, every 0.1s. This is not done yet because it seems to work well enough already. For testing and demonstration purposes, sync.py gets command line arguments for setting progress frequency and showing progress either via listening to signals or polling. |
||
---|---|---|
.. | ||
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