RE: cvs commit: jakarta-tomcat-connectors/jk/native2/include jk_channel.h jk_workerEnv.h jk_worker.h
-Original Message- From: [EMAIL PROTECTED] 1.17 +17 -0 jakarta-tomcat-connectors/jk/native2/common/jk_channel_un.c 1.6 +3 -3 jakarta-tomcat-connectors/jk/native2/common/jk_mutex.c 1.57 +34 -1 jakarta-tomcat-connectors/jk/native2/common/jk_channel_socket.c Henri, IMO all of those should be deprecated. Instead of jk_mutex use the apr_anylock, or apr_thread_mutex cause it's meant for thread locking, not as interposes mutex. and remove the channel_un and channel_socket. MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/native2/include jk_channel.h jk_workerEnv.h jk_worker.h
Mladen Turk a écrit : -Original Message- From: [EMAIL PROTECTED] 1.17 +17 -0 jakarta-tomcat-connectors/jk/native2/common/jk_channel_un.c 1.6 +3 -3 jakarta-tomcat-connectors/jk/native2/common/jk_mutex.c 1.57 +34 -1 jakarta-tomcat-connectors/jk/native2/common/jk_channel_socket.c Henri, IMO all of those should be deprecated. Instead of jk_mutex use the apr_anylock, or apr_thread_mutex cause it's meant for thread locking, not as interposes mutex. and remove the channel_un and channel_socket. Ok for jk_mutex and channel_socket but we should keep channel_un which is requested by many people. In fact it's one of the features of jk2 would convince some admins to use jk2 in favor of jk ;) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]