avro-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <cutt...@apache.org>
Subject Re: Registering multiple classes to a Responder
Date Wed, 15 Aug 2012 19:45:11 GMT
A separate Responder is currently required for each protocol.  If HTTP
is used, different ResponderServlet's can be configured so that
different protocols are run at different URLs.  For NettyServer and
SaslSocketServer one must run different protocols on different ports.

Note however that one can create a protocol that's the combination of
several other protocols and serve that.  For example, with Java
reflection, if you have Java interface A that's one protocol and Java
interface B that's another then you can implement "interface C extends
A, B" and serve that protocol.  Clients that speak either A, B or C
can then connect.  A similar effect can be accomplished with Java's
specific compiler by importing various client protocols into the
server's protocol.



On Tue, Aug 14, 2012 at 6:37 AM, David R Robison
<drrobison@openroadsconsulting.com> wrote:
> I am new to avro and am reviewing the documentation. I am considering
> trying to implement a avro server to run inside JBoss with my other
> services. What I want to do is to register multiple service classes to
> receive avro message. I see in the code the SpecificResponder class that
> allows a single service class to be registered. Is there any way to
> register multiple classes in a Responder?
> Thanks, David
> --
> David R Robison
> Open Roads Consulting, Inc.
> 103 Watson Road, Chesapeake, VA 23320
> phone: (757) 546-3401
> e-mail: drrobison@openroadsconsulting.com
> web: http://openroadsconsulting.com
> blog: http://therobe.blogspot.com
> book: http://www.xulonpress.com/bookstore/bookdetail.php?PB_ISBN=9781597816526
> This email communication (including any attachments) may contain confidential and/or
privileged material intended solely for the individual or entity to which it is addressed.
> If you are not the intended recipient, please delete this email immediately.

View raw message