txsyncml
Limited SyncML 1.1 server. Only implements the “Refresh sync from client only”.
As per the docs (chapter 6.3):
The 'refresh sync from client only' is a synchronization type in which the client sends all its data from a database to the server (i.e., exports). The server is expected to replace all data in the target database with the data sent by the client. I.e., this means that the client overwrites all data in the server database.
Stages of a SyncML Session
Pkg #1 client initialization package
Pkg #2 server init package
Pkg #3 client modification
Pkg #4 server modifications
Pkg #5 mapping of data ids
Pkg #6 mapping status
An initialization package generally contains the following information:
Device capabilities
Requested databases access, type of sync desired
Authentication information
Sync anchors
A modification package generally contains the following information:
Synchronization commands: add, replace, delete, move …
Data ids and contents associated with these commands (except for delete)
A mapping package (only sent by client) generally contains the following information:
Mapping information (a couple of LUID and GUID for each new item added from server)
$ virtualenv ve (ve)$ pip install -e . (ve)$ twistd txsyncml --help
Metadata
Release files for txsyncml 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| txsyncml-0.0.1.tar.gz | 10.2 kB | Details |
Release files / txsyncml-0.0.1.tar.gz
| Download URL | txsyncml-0.0.1.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ecedea13ec845db4b5321d9ab86c416c81e0d2241f0b7525d2a82b76f35c60b1
|
|
BLAKE2b-256 checksum How to use checksums |
518e22eeb81dacf8644413813b6f4c28ade0e2c32c95d820cbe769dd4a3860e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |