Fellow camel users, Camel is my latest hammer and as such I'm trying to use it to build http notification support:
An event for a given user will come in over some channel, and will be routed to one of a finite number of urls that will be looked up in a database given the user. So something like: start-->content-based-router-->(one of 400 http components created at startup). But, I have a couple of questions 1) URL s may be added or changed occasionally and will need to be updated after x without restarting the app. Is it possible to add components after the camel context is started? 2) If I don't want to have a thread per http component, it will be possible for a down listener to slow my system to a crawl waiting 30 seconds for each timeout. Is it possible to mark an http-component as temporarily down so it will fail fast? 3) Is having 400 http components the wrong approach? Is there an httpComponent that will handle multiple arbitrary URLs? Sincerely, Kevin -- View this message in context: http://www.nabble.com/building-a-notification-service-with-endpoints-changing-over-time-tp16945914s22882p16945914.html Sent from the Camel - Users mailing list archive at Nabble.com.
