I will kick off the first discussion item. My personal opinion after
discussing this is:
The beauty of JMX is that it doesn't matter what kind of application
you're using because it is a standardized protocol. The main interest
in having a plugin architecture was that Kitty be compatible with all
types of JMX servers, not just Tomcat. After thinking about this a
bit, it already has that capability, it's just that we decided to
focus on Tomcat because that is where the main need was for
administration, which Kitty solves that problem already.

I think that if we focus on end-user functionality and automation
(performing operations on groups of JMX-enabled servers), Kitty will
satisfy it's mission, and we won't need to get into a hairy complex
plugin architecture right now. I think plugins could be useful for
doing things such as this:
https://issues.apache.org/jira/browse/KITTY-4

But I don't know if it's of value to have such functionality at the
cost of compatibility with all applications. For example, lets say we
really need a plugin architecture, and
https://issues.apache.org/jira/browse/KITTY-4 is the first plugin we
want to write for Tomcat 6, we are going to go through a significant
amount of effort in achieving this. I'm not saying we should throw out
the idea of adding plugin functionality. I just think its not as
high-priority of an item as I originally thought.

I am considering priorities in the Roadmap document to focus more on
distributed operations and usability functionality (gets/sets/invokes
on groups of JMX-enabled systems) rather and bumping down plugins to
the bottom of the list.

Thoughts? Disagreements? Razzes?



On Thu, Jan 20, 2011 at 12:31 PM, msacks <[email protected]> wrote:
> Hi All,
> As promised I have created a 6 month roadmap document for the Kitty project.
> Your commentary is critical in making a decision to move the project
> forward and decide on how to approach the issue of creating a plug-in
> architecture for the project, a task critical to advancing Kitty
> towards a release.
>
> I have made the document world-editable. Please feel free to discuss
> the document on the list, and I will contribute edits, or feel free to
> edit the document directly.
>
> Apache Kitty Roadmap Document:
> https://docs.google.com/document/d/1YN69mJC5LjEzzBy2RvsGSYmKWGLduAOYQSa3T7Gl-Uc/edit?hl=en&authkey=CL2F6qYC
>
>
> Thank you,
> Matthew
>

Reply via email to