On Jul 9, 2009, at 2:46 PM, Iñaki Baz Castillo wrote: > 2009/7/9 Adrian Georgescu <[email protected]>: >> You may extend a resource list with any field you want. The schema is >> extensible is not fixed. In this respect indeed you will end up with >> different implementations that store different fields in different >> ways. >> >> Believe it or not is what vendors pushed IETF to do, so that they >> can lock >> in their customers while using the open standards. > > :( > > >> A practical example. For instance you cannot re-use the contact >> list built >> by Eybeam easily in another client. While is possible to export it >> somehow, >> the opposite is impossible. A resource list composed by other >> client that >> does not have a particular hash value calculated by Eybeam itself >> will not >> be loaded by Eyebeam even if the data is compatible with the >> resource-list >> format. > > This is really sad! >
Do not worry. An alternative is on the way.... Adrian _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
