> On behalf of the jabberd 1.4 team, I'd like to announce a release > candidate for jabberd 1.4.3. It is expected that this will be the > terminal release for the jabberd 1.4 codebase. In order to test this > release, please check out the tagged code from the 'jabberd14' module > on JabberStudio by typing the following command: > > cvs co -r JABBERD_1_4_3 jabberd14 > > For the next week, the jabberd 1.4 team will accept code patches that > fix known bugs in the code (NO NEW FEATURES!). Please send any patches > to [EMAIL PROTECTED] before the end of the day on Wednesday, October 15.
I was just looking at the code of jadc2s in jabberd-1.4.cvs.. there's onw thing I wanted to ask, regarding this code addition: http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/jabberd14/jadc2s/mio/mio.c.diff?r1=1.5&r2=1.6 Is the point of this patch to disable "Nagle" on the listening socket, or on the client sockets? Are socket options inherited from from the listening socket to the client sockets? ( I'm asking this because I'm patching my jadc2s with the SO_KEEPALIVE socket option ) BTW. in jadc2s the log file pathname is hardcoded to be "jadc2s.log" in the current directory.. and this is ugly. -- Damjan Georgievski jabberID: [EMAIL PROTECTED] _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
