>> What about renaming native2 (jk2) in JTC to mod_jk2 >> and jk2_module ? > >+1 if you talk about the binary. -0 if you talk about directory/file >names.
No only source/binary, without touching anything in CVS layout. >> It will be need to rename all non static references, >> variables functions, but I could do that, by suffixing >> with jk2_ : > >If you want, you can go ahead with that ( but in time I would >still like to continue to organize the code with fewer >globals and more objects ) +1 for more globals >> And to be consistent, it could be nice to suffix the native, >> original mod_jk, with jk_ > >> If you agree, I could do this quickly, but JTC developpers >> shouldn't do updates for 1-3 hours... > >I agree with changing the names of non-statics in native2, >but need more time to think about changing dir names. There >are build files, cvs history, habbits that will change as well. No change in CVS tree, just in source to avoid conflict between mod_jk(s) even if one is a jk_module and the other jk2_module .... Rigth now, I'll wait for JTC developpers 'green ligth' to do the changes in JTC native2 ONLY :) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
