-Re: [jira] [Updated] (FLUME-2333) HTTP source handler doesn't allow for responses
Ok, I¡¯ll update the ticket without the 3rd point.
I understand your concern though, and I¡¯ve actually heard it before when
this source was first designed. I¡¯ll create a different ticket for that.
From: Jeremy Karlson <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>
Date: Friday, February 28, 2014 at 11:00 AM
To: <[EMAIL PROTECTED]>
Subject: Re: [jira] [Updated] (FLUME-2333) HTTP source handler doesn't
allow for responses
I am not a committer, but I have no problem with additional changes to this
report or patch item. It's true that the HTTP handler is limited in its
openness for extension and if we can make a few changes to make it better,
I'd be happy to look at any changes you make.
The only thing that I'm uncertain on is point 3. It sounds like the plan
is to build a simple servlet routing mechanism? My gut feeling is that
Flume isn't really intended to be be a servlet container. If things are
that complex, maybe a better choice is to run a standalone Tomcat or Jetty
out front instead? Or alternatively, can the same thing be accomplished
reasonably by running each handler on a separate port (the way it would be
Point 3 sounds like a fair bit of work and I'd hate to see you do that and
have it rejected. Maybe we should wait for some committers to comment
before you start down that path?
On Fri, Feb 28, 2014 at 8:20 AM, Gabriel Commeau