Hi,
It does not have the same type of interceptor interfaces. I think you be
able to used Apollo' security system to restricts which clients can publish
to which destinations. If not, please let lets us know how we could
improve it.
In terms of capturing message traffic, There's an undocumented feature
which lets you filter STOMP frames as they are received by the broker. You
configure it by adding a protocol filter to the stomp protocol. For
example:
<connector id="tcp" bind="tcp://0.0.0.0:61613" connection_limit="2000">
<stomp>
<protocol_filter>my.Filter</protocol_filter>
</stomp>
</connector>
Then you would create a class my.Filter that implements
the org.apache.activemq.apollo.broker.protocol.ProtocolFilter interface
which is defined as:
trait ProtocolFilter {
def filter[T](command: T):T
}
If your class also defines a `var protocol_handler:ProtocolHandler` it will
get set to the protocol hander instance which is being used to handle the
connection.
Hope that helps.
On Tue, Mar 13, 2012 at 9:39 PM, BocaJim <jimw...@gmail.com> wrote:
> Hello all,
>
> We are currently using ActiveMQ with custom interceptors that handle
> security, currently we have thousands of concurrent connections, and plan
> to
> scale to hundreds of thousands accross a cluster...
>
> We use the interceptors to manage authentication as well as to restrict
> which queues a particular client is able to publish to.
>
> We also use the onSend API to capture some message traffic and log it...
>
> I can't find anything similar in apollo, does it exist?
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Does-apollo-support-anything-like-interceptors-tp4470806p4470806.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
**
*Hiram Chirino*
*Software Fellow | FuseSource Corp.*
*chir...@fusesource.com | fusesource.com*
*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*
*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
*
*
*
*
