Noticed that myself :)
It's fixed locally thanks.
---
James
On 28/06/2005, at 8:25 PM, Norman Rasmussen wrote:
> Also in class Statistics, method incomingIq:
>
> command = iq.addElement("query")
> should be
> command = iq.addElement("command")
>
> On 27/06/05, Norman Rasmussen <[EMAIL PROTECTED]> wrote:
>> Read it in context:
>>
>> A responder MUST at least provide an appropriate <identity/> and
>> <feature var='http://jabber.org/protocol/commands'/>, and SHOULD
>> include <feature var='jabber:x:data'/>. It is not required to support
>> additional information about a command. If the command is not
>> available to the requester, the responder SHOULD respond with a 403
>> "Forbidden" error.
>>
>> I interpret that as requiring the response to the query, but you don't
>> need to supply anything more than the identity and feature nodes.
>>
>> Also the current error feature-not-implemented replies should probably
>> have the same id as the requesting stanza, so that clients can link
>> them up.
>>
>> Also I note that: <query xmlns="http://jabber.org/protocol/disco#info";
>> node="http://jabber.org/protocol/commands"; /> generates a disco#items
>> reply.
>>
>> On 27/06/05, James Bunton <[EMAIL PROTECTED]> wrote:
>>> According to JEP0050 it's not required to support additional
>>> information on a command.
>>>
>>> Section 2.2, examples 5 & 6 are what you're referring to right? The
>>> paragraph below states "It is not required to support additional
>>> information about a command".
>>>
>>> What reasons are there for querying the a command node? I can't think
>>> of any extra information it could provide.
>>>
>>> ---
>>>
>>> James
>>>
>>>
>>> On 27/06/2005, at 10:24 AM, Norman Rasmussen wrote:
>>>
>>>> I noticed that the transport node lists
>>>> http://jabber.org/protocol/commands when you get disco#items on it,
>>>> how cool!
>>>>
>>>> Unfortunately the individual commands are REQUIRED in the spec to
>>>> return http://jabber.org/protocol/commands when you get disco#info.
>>>> If you have any time in the next while, can you make it possible to
>>>> disco the command nodes too :-)
>>>>
>>>> FYI: I've been writing nifty patches for Psi to make this work
>>>> nicely
>>>> :-)
>>>>
>>>> On 20/06/05, James Bunton <[EMAIL PROTECTED]> wrote:
>>>>> More commits to CVS everybody!
>>>>>
>>>>> Fixed clientcaps (properly this time I hope).
>>>>> Various exception fixes.
>>>>> Added Ad-Hoc Commands framework.
>>>>>
>>>>> You can retrieve statistics about the transports runtime using
>>>>> ad-hoc
>>>>> commands. Try sending this XML
>>>>> <iq type='get'
>>>>> id='0001'
>>>>> to='msn.host.com'>
>>>>> <query xmlns='http://jabber.org/protocol/disco#items'
>>>>> node='http://jabber.org/protocol/commands'/>
>>>>> </iq>
>>>>>
>>>>> I'm still interested in all your bug reports :)
>>>>>
>>>>> I haven't gotten any statistics about CPU and memory usage from
>>>>> anybody. How's PyMSNt running on your machines people?
>>>>>
>>>>> ---
>>>>>
>>>>> James
>>>>>
>>>>>
>>>>> On 16/06/2005, at 11:09 AM, James Bunton wrote:
>>>>>
>>>>>> Hi again.
>>>>>>
>>>>>> I've committed a small fix to the avatars code that should
>>>>>> increase
>>>>>> compatibility.
>>>>>> Please let me know about any ERRORs that get printed to stdout.
>>>>>> They
>>>>>> report problems in transferring avatars to other users.
>>>>>>
>>>>>> Also, the clientcaps message should now only be sent once, after
>>>>>> the
>>>>>> first text message. So if the switchboard exists only to transfer
>>>>>> an
>>>>>> avatar you won't get a message saying "Please talk to this person
>>>>>> on
>>>>>> Jabber".
>>>>>>
>>>>>> I'd like to know how this version is going memory and CPU wise.
>>>>>> The
>>>>>> RSS reading is the one I'm looking for with memory.
>>>>>> Could you run
>>>>>> ps aux | grep PyMSNt
>>>>>> and read off the CPU and RSS columns after running the transport
>>>>>> for
>>>>>> a
>>>>>> day or so.
>>>>>> Also, please give me a rough idea of how many people are using it.
>>>>>> Thanks.
>>>>>>
>>>>>> Please keep the bug reports coming :)
>>>>>>
>>>>>> ---
>>>>>>
>>>>>> James
>>>>>
>>>>> _______________________________________________
>>>>> py-transports mailing list
>>>>> [email protected]
>>>>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>>>>>
>>>>
>>>>
>>>> --
>>>> - Norman Rasmussen
>>>> - Email: [EMAIL PROTECTED]
>>>> - Home page: http://norman.rasmussen.co.za/
>>>> _______________________________________________
>>>> py-transports mailing list
>>>> [email protected]
>>>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>>>>
>>>
>>> _______________________________________________
>>> py-transports mailing list
>>> [email protected]
>>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>>>
>>
>> --
>> - Norman Rasmussen
>> - Email: [EMAIL PROTECTED]
>> - Home page: http://norman.rasmussen.co.za/
>>
>
>
> --
> - Norman Rasmussen
> - Email: [EMAIL PROTECTED]
> - Home page: http://norman.rasmussen.co.za/
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
