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
