El Viernes, 20 de Noviembre de 2009, Adrian Georgescu escribió: > > Another propietary (even if it's open source) XCAP application? > > good, and > > which client will implement it (uploading an naming an icon in a > > propietary > > way)? Let me guess... Blink? > > Inaki, > > Can you explain what is proprietary about using a random file name for > the icon auid?
The mechanism is propietary as storing a non XML document in a XCAP server is not a IETF/XCAP standard, the naming convention, the transfer mode, the icon image requeriments (size, formats)... all is propietary. Replace "propietary" with "non standard" if you prefer, but the concept is the same: non standard features/specs on top of real standars (SIP and XCAP), so just the clients and servers managed by same vendor (AG) will implement them. But as I already said, the main problem here are the IETF's XCAP specs as they are incomplete and don't provide needed features (as icon storage). But I don't agree if the proposed solution is adding these features using vendor propietary specs. If at least they were really well documented... Regards. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel