On 13-Jul-2009, at 15:15, Peter Saint-Andre wrote:
On 7/13/09 3:44 AM, Fabio Forno wrote:
we are trying to use XEP 144 for synchronizing the roster of our
mobile client with remote services, but we encountered a number of
issues, mainly:
- lack of feedback from the client to the service of which
modifications of the roster have been accepted
- lack of any mechanism for re-synchronizing the roster if
something wen wrong
Therefore we are thinking to extend the XEP in order to address these
issues, the only problem is that we could propose some breaking
changes, therefore we'd like to know if anybody is :
- using the XEP (we know that psi does, but the implementation is
not
very usable, I think for the lack of testing since no transport is
using it)
- planning to use it, in that case any suggestion?
There were some implementations of XEP-0093 in the old old days
(Gabber,
Winjab, etc.), but this has never been the most popular feature. If we
want to design yet another approach, that would be fine with me (if it
fixes all the issues).
I am using it in-house with an ad-hoc command interface, and it works
passably. I'm not sure about the points raised here. Regarding lack of
feedback, this might be considered a feature. My understanding of
roster push is that it merely advises the client to make changes to
its roster and is only concerned with the client having accepted the
changes (even if it didn't employ them). If a client decides not to
take a change a future request for a roster push probably shouldn't
push out that change again (the client already reviewed it and said,
"no").
As for re-synchronizing the roster, as I recall the spec there's no
way to synchronize the roster either. Hence the ad-hoc command
interface, which can be easily extended to do a full push again, if
necessary.
That being said, I'm not the biggest fan of XEP-0144, and would be
keen to see any proposed changes although I lack any of my own at this
time.
-bjc
