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 Plain View
Hadoop >> mail # general >> HTTP transport?


+
Doug Cutting 2009-09-11, 21:41
+
Patrick Hunt 2009-11-12, 22:22
+
Scott Carey 2009-09-26, 00:36
+
Doug Cutting 2009-09-28, 17:01
+
Owen OMalley 2009-09-28, 17:59
+
Doug Cutting 2009-09-28, 22:42
Copy link to this message
-
Re: HTTP transport?

On Sep 28, 2009, at 3:42 PM, Doug Cutting wrote:

> Owen O'Malley wrote:
> > I've got concerns about this. Both tactical and strategic. The  
> tactical
> > problem is that I need to get security (both Kerberos and token)  
> in to
> > 0.22. I'd really like to get Avro RPC into 0.22. I'd like both to be
> > done roughly in 5 months. If you switch off of the current RPC  
> code base
> > to a completely new RPC code base, I don't see that happening.
>
> What transport do you expect to use with Avro?  If wire-
> compatibility is
> a goal, and that includes access from languages besides Java, then we
> must use a transport that's well-specified and Java-independent.  HTTP
> is both of these.  The existing Hadoop RPC protocol is not.
>
> We could adapting Hadoop's existing RPC transport to be well-specified
> and language independent.  This is perhaps not a huge task, but it  
> feels
> to me a bit like re-inventing much of what's already in HTTP clients  
> and
> servers these days: connection-pooling, async servers, etc.
>
Wrt  connection pooling/async servers: Can't we use the same libraries  
that Jetty and Tomcat use?
  Grizzly?

> grate Kerberos with
> Jetty than with a homegrown protocol and server?
>
>
> >   - very expensive on the wire encryption (ssl)
>
> If we don't use HTTP, will we be providing on-wire encryption?  If  
> not,
> this is moot.
>

Yes we are expecting to use encryption down the road.
>
> Finally, need to have secure HTTP-based access anyway, right?  If we  
> use
> HTTP as our RPC transport mightn't we reuse most of that effort?
>
> Doug
>

+
Doug Cutting 2009-09-29, 19:43
+
stack 2009-09-29, 20:38
+
Doug Cutting 2009-09-29, 21:08
+
stack 2009-09-29, 21:57
+
Doug Cutting 2009-09-29, 23:17
+
Devaraj Das 2009-09-29, 23:57
+
Scott Carey 2009-09-30, 01:37
+
Eric Sammer 2009-10-05, 20:43
+
Ryan Rawson 2009-10-05, 20:47
+
Eric Sammer 2009-10-05, 20:53
+
Scott Carey 2009-10-06, 02:59
+
Eric Sammer 2009-10-06, 03:15
+
Scott Carey 2009-10-06, 03:30
+
Owen OMalley 2009-10-08, 22:10
+
Doug Cutting 2009-10-09, 17:49
+
Sanjay Radia 2009-10-09, 18:13
+
Doug Cutting 2009-10-09, 19:56
+
Kan Zhang 2009-10-14, 01:59
+
Doug Cutting 2009-10-14, 16:37
+
Kan Zhang 2009-11-06, 19:15
+
Doug Cutting 2009-11-06, 21:06
+
Kan Zhang 2009-10-14, 17:45
+
Scott Carey 2009-10-11, 01:11
+
Scott Carey 2009-10-06, 03:19
+
Scott Carey 2009-09-30, 03:06
+
Ryan Rawson 2009-09-30, 03:20
+
Raghu Angadi 2009-09-29, 22:11
+
Doug Cutting 2009-09-29, 23:35
+
Sanjay Radia 2009-09-30, 23:04
+
Sanjay Radia 2009-10-05, 16:41
+
Doug Cutting 2009-10-05, 23:48
+
Sanjay Radia 2009-09-28, 20:13
+
Ryan Rawson 2009-10-05, 20:57
+
Eric Sammer 2009-10-05, 21:13
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