Rick Jones wrote:
what are the implications for having the application churning away doing
application things while TCP is feeding it data? Or for an application
that is processing more than one TCP connection in a given thread?
It almost feels like the channel concept wants a "thread per connection"
model?
No, it means only that your application must be asynchronous -- which
all modern network apps are already.
The INN model of a single process calling epoll(2) for 800 sockets
should continue to work, as should the Apache N-sockets-per-thread
model, as should the thread-per-connection model. All of that continues
to be within the realm of application choice.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
