On Friday 20 July 2007 23:45, Tomasz Sterna wrote: > Hi. > > I'm going to extend jabberd2 component protocol to allow components > access to user roster and presence information. > (Mainly for PEP and transports :-) > > But before I do it I wanted to make a sanity check if the idea makes > sense. > My proposed changes are described on > http://jabberd2.xiaoka.com/wiki/ComponentProtocol > > Any comment is welcome.
As far as I know people from ejabberd and others work on extending component protocol - XEP-0114. I think it is worth synchronizing efforts. I am not sure if you are refering to XEP-0114 but all such stuff could be included in XEP-0114 so all servers could have similar functionality accessible through the same protocol. Regarding your extensions. It looks good to me. I would like to see <route> element defined and added to XEP-0114. On top of functionality you described in your document I would also add functionality for activating user session from external component. The use case: Let's say the user has a VoIP device which doesn't support XMPP but the device connects directly to a service which does support XEP-0014. So when the user (VoIP device) is online the external component could activate session for the user so presence would be available for the user. Together with capabilities it would allow VoIP communication for other users with clients supporting VoIP protocol. Artur -- Artur Hefczyc http://www.tigase.org/ http://wttools.sf.net/
