В сообщении от Понедельник 15 Май 2006 08:02 Trejkaz написал(a): > On 15/05/2006, at 11:58 AM, Tobias Thierer wrote: > > Is the following a legal XMPP packet (linebreaks inserted for > > readability)? > > > > <iq id="rpc-0wLET-8" to="[EMAIL PROTECTED]/Biomatters" > > type="set"> > > <query xmlns="jabber:iq:biomatters:rpc" version="1.0"> > > <methodCall> > > <methodName>add</methodName> > > <params> > > <int>23</int> > > <int>42</int> > > </params> > > </methodCall> > > </query> > > </iq> > > It is. > > > <iq id="rpc-WRH8A-8" to="[EMAIL PROTECTED]/Biomatters" > > from="[EMAIL PROTECTED]/Biomatters" type="set"> > > <query version="1.0" xmlns="jabber:iq:biomatters:rpc"> > > <methodCall> > > <methodName></methodName></methodName> > > <params> > > <int>23</int> > > <int>42</int> > > </params> > > </methodCall> > > </query> > > </iq> > > Are you sure this is what's actually coming out of the server? My > bet is that whatever library you're using to print that packet out > has either parsed it incorrectly, or is formatting it incorrectly. > If you run tcpdump or similar, you should be able to see what the > server is actually sending. "tcpflow -c" is much more suitable for this purpose. It do not prints out IP headers or hex data, just IPs, port numbers and stream contents.
> TX -- Respectfully Alexey Nezhdanov
