[jdev] File Transfer Interoperability
alex at jivesoftware.com
Mon Aug 6 15:24:08 CDT 2007
I do like the idea of an alternative namespace as well. The reason we went the route we did was we thought it would be low impact from a protocol standpoint and wouldn't cause the sort of issues it did. I will work on writing a XEP that encompasses the functionality we desire and bring it before the group.
----- Original Message -----
From: "Justin Karneges" <justin-keyword-jabber.093179 at affinix.com>
To: "Jabber software development list" <jdev at jabber.org>
Sent: Monday, August 6, 2007 12:41:06 PM (GMT-0800) America/Los_Angeles
Subject: Re: [jdev] File Transfer Interoperability
> > Spark uses a special variant of XEP-96 that apparently breaks
> > compatibility with every other client, most likely due to x:data
> > ambiguity. I'd suggest the Spark guys make an extension that is less
> > prone to misinterpretation.
> I don't know what the best solution is in this situation. We want Spark to
> be compatible as can be in this case but if we were to move to strictly
> interpret the XEP this would cause a degradation in the file transfer
> experience in Spark, as you can see it was a lose, lost situation.
As I wrote, maybe it is possible to make an extension that won't be
misinterpretted. Rather than fiddling with the x:data form, how about going
the traditional route and adding some new namespaced elements/attributes?
We can take a time machine back to 2003:
More information about the JDev