Correct me if I am wrong but isn't Hadoop moving towards the Avro IDL for full RPC (in either 0.23 or some later version)?
Matt From: Koert Kuipers [mailto:ko...@tresata.com] Sent: Wednesday, September 21, 2011 4:00 PM To: hdfs-user@hadoop.apache.org Subject: Re: A question about RPC i would love an IDL, plus that modern serialization frameworks such as protobuf/thrift support versioning (although i still have issues with different versions of thrift not working nicely together, argh why is that). the only downside is perhaps that they are a little slower than writables. On Wed, Sep 21, 2011 at 3:12 AM, Uma Maheswara Rao G 72686 <mahesw...@huawei.com<mailto:mahesw...@huawei.com>> wrote: Hadoop has its RPC machanism mainly Writables to overcome some of the disadvantages on normal serializations. For more info: http://www.lexemetech.com/2008/07/rpc-and-serialization-with-hadoop.html Regards, Uma ----- Original Message ----- From: jie_zhou <jie_z...@xa.allyes.com<mailto:jie_z...@xa.allyes.com>> Date: Wednesday, September 21, 2011 12:12 pm Subject: A question about RPC To: hdfs-user@hadoop.apache.org<mailto:hdfs-user@hadoop.apache.org> > Dear: > > Nice to meet you! > > I am a beginner of hadoop. Recently, I have seen the source of RPC of > hadoop,but now I have a question. As we know,hadoop RPC make use > of Dynamic > proxy mechanism ,but > > why not use IDL such as CORBA, or AIDL of Android? > > Thanks for your early reply. > > Best Regards, > > jie > > > > > > > > > > This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. The information contained in this email may be subject to the export control laws and regulations of the United States, potentially including but not limited to the Export Administration Regulations (EAR) and sanctions regulations issued by the U.S. Department of Treasury, Office of Foreign Asset Controls (OFAC). As a recipient of this information you are obligated to comply with all applicable U.S. export laws and regulations.
