[JDEV] Jabber Client Compliance

Steven Brown swbrown at ucsd.edu
Wed Aug 6 21:59:14 CDT 2003


> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Iain shigeoka
> Sent: Wednesday, August 06, 2003 3:21 PM
> To: jdev at jabber.org
> Cc: compliance-jig at jabber.org
> Subject: Re: [JDEV] Jabber Client Compliance
>
>
>
> On Wednesday, Aug 6, 2003, at 11:10 US/Pacific, Julian Missig wrote:
>
> > I'm getting really sick of looking at my roster and seeing things like
> > <presence from="some at jid"
> > to="julian at jabber.org"><show>normal</show></presence>
>
> :)
>
> > I know that Jabber Compliance Testing is one of those things that
> > people keep talking about doing and saying we will do someday, etc,
> > etc., but I'd like to propose that we start doing this stuff *now*.
>
> The JSF is working on compliance although right now it is in quiet
> development and and the first compliance testing target is servers not
> clients. Client testing ends up being a lot harder than server testing
> so we punted and went for servers. I definitely agree there is need for
> client compliance testing. I've Cc'd the compliance-jig@ list and I'd
> love to have you follow up there. We have a jabbercollab project setup
> for compliance already if you're interested in joining the team, let me
> know. You can always sub to the compliance-jig list to get the
> discussion going. If we start creating code then perhaps a jabberstudio
> project would be needed.
>
> The JSF is eager to get client compliance testing underway but simply
> don't have the resources to do it (primarily people's time - we can get
> funding if there is things that need funding).

As a simple step, could a patch/branch to the Jabber server be made that
checks for common client protocol mistakes and writes debug log messages for
them?  That'd make it easier for client implementors to find their bugs - by
testing against such a modified server.  It could also totally reject
fully-invalid things like <show>normal</show> and return a presence error.




More information about the JDev mailing list