[ 
https://issues.apache.org/jira/browse/NIFI-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278695#comment-14278695
 ] 

Adam Taft edited comment on NIFI-221 at 1/15/15 2:03 PM:
---------------------------------------------------------

After thinking about this some more, I believe this can/should be done as a 
single processor.  In a single processor design, the processor opens a socket 
and listens for incoming connections, routing requests as described in 
HandleHttpRequest.  However, the flowfile input queue for the processor is used 
as the signaling mechanism coming from the backend.  i.e. the input queue of 
the same processor takes the place and responsibility of the HandleHttpResponse 
processor.

In this design, there's no controller service to be configured nor two 
processors that need to be added.


was (Author: taftster):
After thinking about this some more, I believe this can/should be done as a 
single processor.  With this design, the processor opens a socket and listens 
for connections, routing requests appropriately, as described in 
HandleHttpRequest.  However, the input queue for the processor is used as the 
signaling mechanism coming from the backend.  i.e. the input queue of the same 
processor takes the place and responsibility of the HandleHttpResponse 
processor.

In this design, there's no controller service to be configured nor two 
processors that need to be added.

> Build Processors that allow for receiving and responding to arbitrary HTTP 
> requests
> -----------------------------------------------------------------------------------
>
>                 Key: NIFI-221
>                 URL: https://issues.apache.org/jira/browse/NIFI-221
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>
> The idea here is that we can receipt an HTTP request and use NiFi, in essence 
> to build a web server graphically. This opens up a wide range of 
> possibilities, by allowing a DFM to easily add a web front-end to any service 
> that NiFi can interact with or to perform any sort of action that NiFi has 
> the ability to perform, such as data format conversion, etc.
> For example, if you want to provide a web-based front-end to an SFTP Server, 
> you could do so by creating a flow like:
> ReceiveHTTPRequest -> PutSFTP -> RespondHTTPRequest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to