[jdev] PyMSNt 0.5 released

James Bunton james at delx.cjb.net
Fri Sep 3 02:59:34 CDT 2004

On Fri, 3 Sep 2004 08:23 am, Peter Millard <pgmillard at gmail.com> wrote:
> Message: 4
> Date: Thu, 2 Sep 2004 15:01:41 -0600
> From: Peter Millard <pgmillard at gmail.com>
> Subject: Re: [jdev] PyMSNt 0.5 released
> To: Jabber software development list <jdev at jabber.org>
> Message-ID: <cfd3c4d104090214011b6872b5 at mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
> On Thu, 2 Sep 2004 07:49:22 +1000, James Bunton <james at delx.cjb.net> wrote:
> > * If a contact changes their nick you'll see it
> This COULD be the cause of the serious performance problems we're
> seeing on jabber.org. I'm wondering what the motivation is behind this
> change was? Jabber has ALWAYS valued MY setting of your nickname, over
> yours. The problem that I think we're seeing is that some MSN clients
> change folks nicknames as they change their presence (like from "pgm"
> to "pgm-away"). This results in a change to everyone's roster who has
> me in there. This is BAD since it can easily over-whelm XDB data
> stores. (It's no so bad until you have 200k+ users :).
> I'm hoping this change can be rolled OUT of this release? And possibly
> have server admins revert back to an older version until this can be
> fixed.
No, that's definitely not the problem. All that happens when an MSN user 
changes their nick (or all that's supposed to happen) is a <presence 
to="jabberuser at host"><status>MSN nickname</status></presence>

I agree with you entirely, I really dislike the official MSN client, with one 
of the main reasons being because of the nickname thing. But it's sometimes 
important to be able to see what people have as their nicknames, so it's 
mapped to a status message. Which is pretty much what most MSNers use it for 

> Not sure if any other BIG public servers are getting hit by this, but
> I've seen our load our main server skyrocket today. I _believe_ this
> is the cause.
hmm.. I'll look at it. I did notice a bug like this ages ago, but I thought I 
fixed it.



More information about the JDev mailing list