We certainly need to make it easier for any parts of a route (be it a consumer, processor, bean or whatever) to be able to pause/resume, start/stop existing routes.
2009/1/7 huntc <hu...@mac.com>: > > Hi James, > > Not quite the same use-case - it is perfectly valid for either of my tcp > endpoints to close the connection. I was looking for a way to synchronise > any closure with the other endpoint. > > I did start investigating this and saw that a MinaExchange was being passed > downstream. From that I could close the upstream connection given that the > MinaExchange allowed me to resolve the MINA IoSession. However I didn't get > to the point where the upstream endpoint could see the downstream endpoint's > IoSession... and then gave up because my customer decided that I should > spend more time on this and re-write the Perl service using Camel. This now > eliminates my original use-case. > > Thank you for replying. > > Kind regards, > Christopher > -- > View this message in context: > http://www.nabble.com/Dependent-endpoints-tp21286657s22882p21341273.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
