-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/15/09 9:36 AM, Jiří Zárevúcky wrote: > 2009/7/15 Peter Saint-Andre <[email protected]>: >> On 7/15/09 9:12 AM, Jiří Zárevúcky wrote: >> >>> We probably first need to sum up the additional functionality we'd >>> want in roster management. >>> Arbitrary attached XML is the first and obvious one, which wouldn't >>> even require a new protocol. >> Correct! The "X" in XMPP stands for "extensible". :) So maybe we need a >> service discovery feature for roster extensions and away we go. No need >> for a redesign of jabber:iq:roster at that point! >> > > You've got a point. > > But let's look at this from another perspective. XMPP-IM doesn't > dictate jabber:iq:roster has to be used, right? Then there is nothing > wrong if a few people with a lot of free time write a purely > experimental XEP defining a new way to access and manage roster. > Developers who like the idea could just play with it... no obligations > for anyone else. :) > > Well, that's the theory, anyway. The question is whether more people > would be interested in such experiment. :)
For sure! Experimentation would be very beneficial in this area. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpd+NEACgkQNL8k5A2w/vys9gCgnC3n6HArYKeJVijVCDNtmH7e G8sAn0bxRKJrmsISBs3uZZBg/1Yq51Bs =lAp+ -----END PGP SIGNATURE-----
