Hello Asankha, > Synapse would be expected to work with many messages concurrently > (acting as an ESB) we do not want a huge number of threads to be doing > IO - and hence the requirement for an async http client.
Thanks for the update, I will consider this around christmas time. For the records: Let m be the number of messages processed concurrently and c the number of connections opened concurrently. The original idea of HttpAsync - without NIO - was to have O(c) threads for handling I/O, with a maximum of 2*c for maximum throughput and a minimum of c. With NIO, we can get that number below c as we don't need one thread per connection for receiving messages. But even without NIO, 2*c or c could be a significant improvement over O(m). Still, there is no point in pushing HttpAsync until we've figured out HttpCore and how to deal with opening connections. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
