 <p>Sounds like you need some sort of a mechanism to correlate requests to the different plugins available. Ideally, there should be a different URL path per set of operations published for each plugin. </p> <p>I would consider implementing a sort of map/dictionary of URL paths to plugins. Then for each request received, do a lookup in the map and get the associated plugin and send it the request accordingly. If there is no entry in the map, then a redirect/proxy could be sent. For example if URL = <code>http://yourThriftServer/path/operation</code>, the operation or the path <strong><em>and</em></strong> operation would map to a plugin.</p> <p>An extra step would be to implement a sort of meta request, whereby a client could query what URL paths/operations are available in the server.</p>