-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alan Woodland, 2010-05-21 11:40: > My main concern now is how we support this for the duration of > squeeze. It seems likely that at some point the version we ship will > cease to function with the mozilla.org servers, in which case the > package either needs updating or removing. We could of course work > around it by packaging the server-side components as well, but I > suspect most users will be interested in syncing with mozilla.org, not > running their own server.
I' also involved in the development of a Python/Django based server-side component[1] for Weave and I can say that the server is content-agnostic i.e. it only cares about two types of objects: WBOs: Weave Basic Objects: Stores ID, parent ID, username, sortindex and a payload which is plain JSON. Collections: Stores a subset of WBOs. All the logic is on the client side and changes in the storage format should only occur in the JSON payload. The only problem I can see is if people use different versions of the Weave client as this could lead to different formats for the payload getting pushed to the server (which would mess up older/newer clients). Plus, the server API is designed to handle different (read older) versions by placing the Weave API version in the URL. [1] http://code.google.com/p/django-weave/ - -- Michael Fladischer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv2WYsACgkQeJ3z1zFMUGYssgCeJdCKCE/eSDGCXTNyTpGwsMgu 3rIAniffoe7D1UjJ6Kl3DJoldO/naOwn =X9E6 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
