activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From artnaseef <...@artnaseef.com>
Subject Re: ActiveMQ Console - let's get the problem defined
Date Tue, 04 Feb 2014 04:27:10 GMT
By the way, on the topic of using an external console to replace the current
built-in console, there's very real concern with circular dependency.

If the external console contains ActiveMQ-specific parts, such as listing
Queues and Topics and giving operations on the same, then changes to
ActiveMQ internals could necessitate changes to the external console.  And
visa versa.  This would make releases of both difficult any time a change
was made to either.

Circular dependencies in software are a very bad thing.

I've added a line in this regard on the "PROBLEM STATEMENT" doc.

To try to make my position more clear:

   BAD
   external console code requests list of queues from broker

   GOOD
   external console code requests list of all entity types from broker
   user chooses Queue from the same list
   external console code requests list of all entities of type Queue (as
chosen by the user)




--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Console-let-s-get-the-problem-defined-tp4677105p4677371.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Mime
View raw message