On Sat, Nov 29, 2003 at 10:34:18PM -0500, Paul Curtis wrote: > When using AIM with jabberd2, the AIM transport doesn't handle browse > packets. In jabberd 1.4.x, this wasn't a problem as you could configure > the JSM to respond with browse information as configured in the > jabber.xml config file. Jabberd2 doesn't have this capability, and so > browsing to AIM will produce an empty list. This is a bit disconcerting > to the users, since they cannot browse to register with the transport. > MSN is better, as it handles browse packets, and returns a response.
You can configure the transport in the static list in sm.xml like this: <item category='gateway' type='aim' jid='aim.example.com' name='AIM Transport'> <ns>jabber:iq:register</ns> <ns>jabber:iq:gateway</ns> </item> <ns> is not really documented either. I should add something to sm.xml about it, as its used for agents compat as well. I agree that components should provide disco #info for themselves. Most of the time it will be dead simple - just a static response. Rob. -- Robert Norris GPG: 1024D/FC18E6C2 Email+Jabber: [EMAIL PROTECTED] Web: http://cataclysm.cx/
signature.asc
Description: Digital signature
