Hi Mike, > I don't have much experience (none actually) with creating Http > servers, but I assume they must perform some kind of connection pooling > in order to support keep-alive connections.
No, they use thread pools. Once an incoming connection is accepted, a service thread is allocated for handling all requests coming in through that connection, sequentially. > The use case is more > similar to asyc/pipelined requests though I guess. Do we envision > adding support for this kind of thing, or will that be left to the > future and http-infra? I guess we'll need something along that line for testing pipelining. http-infra sounds like the place for it. > > The motivation for introducing the http-conn component was not to > > use it on the client and server side, but to have it available > > without depending on http-client. > > So this is primarily for http-async support? Yes. cheers, Roland
