As I mentioned, there's a lot of duplication - and likely we'll see more. I don't see this as a major problem - duplication is sometimes good. It would be however nice to have similar behavior when possible and make sure we pick each other's fixes.
The areas of duplication: - starting and embeded machine using JNI. The code seems similar, I did reviewed it in daemon and didn't find anything to grab - but more eyes to look at the code would help. - starting a VM using exec / monitor the child process. It is not implemented yet in jk2 - but pretty important ( it's one of the features from jserv that wasn't yet ported). It seems daemon has a bit of code - as I mentioned from reading it I don't think it works, and it would be better to use the code from jserv for this - whenever we do implement this. - configuration for started processes. Daemon is using CLI, jk uses a file - nothing to do here ( but it would be good if daemon would use properties too ). - Win32 services. This is not yet ported to jk2 - and I'm not sure what to do about jk_nt_service. It works very well, but the code is messy. It would be worth adding a jk2 component in the style of the win32 event log. - chuid/kill. The code in daemon seems very good - that's what I'm using for jk2_user ( I'll check it in after I test more ). As Mladen mentioned, it may be usefull to have an asynchronous channel between tomcat and the web server. It is also very usefull to add the 'monitor/exec' features from jserv. And if we integrate the features from nt_service, jk2 will have all the code that's needed for launching. So it may be worth adding a small 'main()' to jk2. It would read a config - including components that would start/monitor tomcats, async communication, manage the shmem ( so that tomcat doesn't have to use JNI ), etc. Most of the code is already available - in either daemon or jserv. The main questions are 'when' and 'who'. For the first - I suspect not the near future, unless more people are interested and volunteer for the 'who' part :-) -- Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
