"keep alives" and the StandardHttpContextMap

[James McMahon <js...@gmail.com>]

An application POSTs to a HandleHttpRequest processor. As I understand it,
an entry is created on the StandardHttpContextMap.

For any number of reasons a "keep alive" is sent following the initial
POST. Is another unique identifier placed on the context map for the "keep
alive", or - being associated with the original request - does the "keep
alive" not result in its own unique identifier on the context map?

I need to discard zero-sized "keep alive" messages from my flow. I first
need to understand whether discarding them will leave orphan identifiers on
the context map. That would be an issue; eventually I will exhaust the
context map.

I also need to understand whether responding to the "keep alive" will cause
removal or the identifier associated with the *original* request from the
context map? That would also be a problem, because then when I later try to
respond to the initial request an error will be thrown. There will no
longer be an identifier for the original request on the context map.

What is the best practice for handling this situation? I am using NiFi 0.7.

Jim