Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Avro >> mail # user >> Avro Client-Server - generic vs specific


Copy link to this message
-
Avro Client-Server - generic vs specific
Hello,

We have got two ways of creating an RPC communication protocol from AVDL.

Generic:
https://github.com/matteobertozzi/Hadoop/blob/master/avro-examples/java/ipc/HTServer.java
Specific:https://github.com/phunt/avro-rpc-quickstart/blob/master/src/main/java/example/Main.java

Specific provide a custom implementation (it require code generation
based on avdl) while generic provide 'generic' implementation. What this
*generic* actually means in terms of a protocol specification and code use?

1. What is the difference between the two apart from code look?
2. I can not understand what would be a good example code showing the
advantages of Specific vs Generic responder?
3. When would be the good choice to use *generic* and when *specific
(code generation?)* responder?

thank you in advance for your time replying.

Mick
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB