Andrzej,
In OSS projects that's the way sometimes things are... which is not to mean that we shouldn't improve as a community ;-) You've made a lot of valuable contributions, and I personally value highly your involvement in the project, so please don't get discouraged.
Sorry I wasn't clear, right I'm a bit frustrated but that does not mean that I do not will do the jmx stuff and this does not mean that i stop contribution.
I just wish to address with dramatic words some problems we run into from my point of view.
I think we have actually to many open issues for making such a big step like porting to jmx.
I wish to hear yes form the community, jmx is good for nutch, we had discussed positive and negitive issues.
Actually i have the feeling people think, well let him do what he want we will see if this is useful.
I'm quite interested in helping you to integrate the other content parsers that you contributed in your original patch.
That would be great, may be you can use the new wiki page as well.
I see, i was sending some further reading links with my document. I think we should discuss jmx independent of the feature nutch architecture.We haven't tools anymore we will have a server that runs 24/7 and a set of components that can be triggered.
There was just one comment by Doug about my jmx mail and nobody else give any technical comment. That strongly remembers me to the time I was sending my first concept about the plugin system to this list.
See above - I think many of us who hang around on the lists are not too experienced in JMX. Hence, we are not able to provide any sensible comments this or that way - I can at least speak of myself here... ;-)
Is nutch a webapp and a set of command line driven tools or a server that does as much as possible self managed just configured by a webbased gui?
In case we stay with the command line tools we will miss a lot of user that searching for a 'plug and play' intranet search engine.
At least jmx is one technology to create a 'nutch server' we could use a micro container like spring or pico container alternatively.
What i wish to say we need to discuss it, since again moving from command line tools to a server architecture is not that much work by using jmx but a lot of work in the minds of all developers and users.
Thanks for your feedback.
Stefan
--------------------------------------------------------------- enterprise information technology consulting open technology: http://www.media-style.com open source: http://www.weta-group.net open discussion: http://www.text-mining.org
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
