Hello Thanks for your comments and corrections.
Ad section 3: The purpose is to fulfill the requirements brought up by Dave Cridland but useful to many others, mainly corporate networks and big social networks. PEP-publishing is insuitable for these use cases but mimicking the fetching and notification keeps read access working. All boils down to just specifying a name of an ad-hoc command to be tried if PEP-publish is forbidden. The only catch is that it is a slightly extended PEP ;). Cheers, Pavel On Wed, 27 Aug 2008 12:03:18 +0100 Pedro Melo <[EMAIL PROTECTED]> wrote: > Hi, > > On Aug 27, 2008, at 1:04 AM, Pavel Simerda wrote: > > > I prepared the long-promised examples of > > possible XEP-0154 protocol flows. > > > > http://www.pavlix.net/xmpp-profile.txt > > Some typos: > > * in Example 8, I think you mean <feature > var='urn:xmpp:tmp:profile:basic+notify'/ > >, per secion 10.2 of XEP 0060; > * there is a lost http://jabber.org/protocol/tune in Example 9 and > 10; > > I need to re-read section 3 with more time, I don't understand what > is its purpose yet. > > But the rest seems fine. > > Best regards, -- Web: http://www.pavlix.net/ Jabber & Mail: pavlix(at)pavlix.net OpenID: pavlix.net
