On 1/15/02 7:45 AM, "Thomas Muldowney" <[EMAIL PROTECTED]> wrote:
> Hey all it's about time for a new development cycle for jabberd. This Great! > - General cleanup and standards compliance. This includes checking all > the error reporting to make sure it makes sense, and all the other > little oddities that have slipped in. Fantastic. While this is being done, I would really (really really) appreciate it if someone would create a list of exactly what error codes are reported in what situations. That would greatly help client writers react properly to error codes and help independent server implementers provide the uniform error reports. > - One I just thought of while typing this all up is a build option that > only builds the server with options that have been approved by the > council. This would currently be pretty lean, but it would supply a > standards benchmark for other server developers to look at. That would be also very helpful. A test suite to test that functionality would be even better! :) -iain _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
