Have not seen a response from the Nifi team on this. Can someone from the team, please share their views on this.
Thanks Paresh From: Paresh Shah <[email protected]<mailto:[email protected]>> Date: Tuesday, March 8, 2016 at 11:58 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: EndpointConnectionPool is not reusable. We have a use case where we would like to perform some routing based on application defined strategy. In order to be able to do this we need to have a mechanism to pass in the selcted nodes based on the app strategy. Ideally we would like to pass this strategy into the EndpointConnectionPool. Currently we see that the EndpointConnectionPool is not implemented as an interface and thus SocketClient explicitly contains an instance of this class. Also the logic to perform the load balancing is buried inside the EndpointConnectionPool. Are there any plans in the near term to make these components extensible. Thanks Paresh ________________________________ The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________
