[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [higgins-dev] Enhancement proposal for the CardSync protocol
- From: Markus Sabadello <msabadello@xxxxxxxxxxxxx>
- Date: Mon, 13 Apr 2009 22:07:46 +0200
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=Itif5WQciXydVrAHT3xJjJv2mahGiD8RgHDfP6xfGIQ=; b=aTJvjdNJ4ViyWTvVtrbUkHOqTWgSuGBuzZth3uL836z+7skStm2brO3rVi4fXNGpLO 2KP/iK8+XD7ieUUmjPBxJ/zUN+lCJVLioyd2Bx6QLMCvZTNUSaTDRaL3BpdMLZU+s77Y fkUMpAboTYp+5ILWPnaJHRuRkQn99dgqaFtmM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Fz17ECA7EsqzMXp6w9H6NfkvN2t3tzAvEOK+AH06PKQc304VkHBfknFNxMXQmzCKLy oJsPXm6CRb6HecL9jQRLDX8iX2pAIBI+dsf6IKuM30D/7lO7VYWtURJb9cUNaaPVVvPm +KJEyjeh0UTeoGV5BxEI3SIWOFM/OtDtuQWjA=
Nice to see you on the list :)
I've never heard of XCAP, but I just went through that PPT. It looks like a great technology.. It seems to be very suitable when you have backend data in XML format and want to expose that data.
In the CardSync protocol however, we don't really have XML data in the backend. We only use it in the protocol. RPPS stores cards in a database, not as .crd files. Also, in the "Update Card" message (http://wiki.eclipse.org/CardSync_JAX-RS_API#Update_ICard), the XML format is different from the .crd format of a card.
So I think XCAP would be overkill here. But I'm not sure, maybe Alexander has a different opinion (he mostly designed CardSync).
BTW Antoine, any news on the iPhone Selector? Did you try to build it yourself?
On Thu, Apr 9, 2009 at 3:46 PM, Antoine Fressancourt <af.devlist@xxxxxxxxx>
I am a R&D engineer from Atos Worldline, one of the companies involved
in the FC² project in France. We had the opportunity and the chance to
meet with Paul Trevithick and Markus Sabadello in France during a 3
days meeting in April when some details about the Higgins project and
the components architecture were presented to us. During this meeting,
we learnt about the cardsync protocol, which is an XML document
exchange using a RESTful interface.
I have a suggestion to make about this protocol. In the wiki
documentation, the messages exchanged to create, update or destroy a
card in the cardstore. Indeed, I am a bit sceptic about the method
used to update a card. From my understanding, when somebody wants to
update an information on a card, he has to send the whole content of
the file in XML, with the update included. It seems to me that this
procedure could be enhanced by using XCAP.
XCAP stands for XML Configuration Access Protocol. Basically, this
protocol allows a person interested in a particular data in an XML
document to access it directly. The path of the XML node in the
document is mapped to an URI, which can be used to create, update or
destroy the node. As I am sure this explanation is not enough for you,
I can indicate you an excellent XCAP tutorial written by the principal
author of the XCAP RFC.
Currently, this protocol is used in Telecommunication services such as
Presence service or contact list management in order to maintain
contact lists or user profile in a central node called the XML
Document Management Server. As this server has about the same role for
these services as the CardStore in the Higgins architecture.
I make a suggestion here, and I would be pleased to answer your
remarks or questions if you have some.
higgins-dev mailing list