For Freenode, the right way would be to have Chanserv managed channel that is
registered under the PMC, it should be #apache-activemq
Then ops and such can be changed.
On Tue, Apr 14, 2015 at 12:43 PM, Bruce Snyder
wrote:
> I don't really care one way or the other. However, the problem wit
Thanks
On Mon, Apr 13, 2015 at 9:56 AM, Rob Davies wrote:
> Folks - if anyone has cycles - can they start looking at accepting some
> of these pull requests into the ActiveMQ code base:
> https://github.com/apache/activemq/pulls ?
+1 Artemis
On Tue, Apr 14, 2015 at 9:43 AM, Hiram Chirino
wrote:
> Now that we have chosen to give the HornetQ code donation a code name,
> it's time to pick what that code name will be. Please select from one
> of the following options:
> [a] ActiveMQ Artemis
> [b] ActiveMQ Luna
> [c] ActiveMQ
I think what I’m trying to say is that - OpenWire is a two way communication
protocol,
it benefits in producing from you not closing the connection (you are just
causing broker connection
management churn) and some of the features really requires that a connection
isn’t man in the middle
man
Been quiet on this for a long time.
I am a contractor, not a committer, nor PMC, I’ve done countless hours of
ActiveMQ classes, training and consulting.
davsclaus commented 5 hours ago
No description provided.
davsclaus commented 5 hours ago
There were 2 left over comment
I think you are going to have more problems with this than it is worth
- Openwire and TCP is much more of a two way protocol, especially concerning
cluster update features and rebalance, the brokers
need to be able to fully communicate with the client for this to work.
The client and cluster
