Thanks Joe for the pointers.
On Wed, Oct 14, 2020 at 3:31 PM Joe Witt wrote:
> Right makes sense. They're waiting for the completion of the response as
> the payload to pass on. If we need incremental handling of the response
> body then we need to factor that into a given processor.
Right makes sense. They're waiting for the completion of the response as
the payload to pass on. If we need incremental handling of the response
body then we need to factor that into a given processor. InvokeHttp or
something like it is a good candidate. Almost a sort of 'InvokeHttpRecord'
Hello,
I tried both getHTTP and invokeHTTP (but didn't try all options). What I
need is to deal with the cases, such as SSE (Server Sent Events) which
works with long polling. Meaning the client initiates a connection (via a
HTTP request) to the SSE server, the server keeps the connection open
Clay
Have you evaluated whether InvokeHTTP will give you the desired behavior
for your case - in particular with a long timeout perhaps? If you have and
it doesn't do the job do you mean something which initiates a request to an
HTTP server then assumes the response will remain open and it
Does NiFi have a processor that can act as a client for a long polling
server, for example an SSE server?
More specifically, I want a client that can issue a HTTP GET request to a
long polling server and accept stream of messages from the server (on the
same connection).
If there isn't one, which
