Not quite. transportConnectors are for message consumers/producers (ie clients).
networkConnectors are for broker-to-broker communications. If you only have a single broker, you can remove all networkConnectors (probably a good accepted practice). As you can probably imagine, brokers have different concerns when passing messages to other brokers, than to consumers. ----- "j0llyr0g3r" <[EMAIL PROTECTED]> wrote: > Hey folks, > > What is the difference between a "transportConnector" and a > "networkConnector"? > > The documentation says "Todo", google didn't help me as well..... > > I assume the following: > > A "transportConnector" specifies the Port(s) to which a broker listens > for > connections, __regard__ wether this connection stems from another > broker or > a consumer or a producer > > A "networkConnector" specifies the hosts to which the broker sends > messages, > __regard__ wether this host is another broker or a consumer or a > producer > > Could please somebody confirm this? > > Thx for all replies guys..... > > -- > View this message in context: > http://www.nabble.com/difference-between-transportConnector-and-networkConnector-tf4191804s2354.html#a11920763 > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
