Hi Oleg, > I played around with various options and found none of them satisfactory > enough. I still think we may be able to do away with #prepare() method. > There will be no need to "announce" an unconnected socket the connection > at all we somehow manage to provide a mechanism to look up the socket by > the HTTP request. This way we could abort request's execution by simply > closing the socket. No need to muck around with the connection. > > Let's move onto other issues and deal with this one later
Ok. I'll try to get some work done on the connection manager this weekend. Not sure how much time I'll find though - the Snooker Masters is on TV :-) I'll focus on the implementation part, test cases will follow once we have an understanding of how the API will shape up. Here's a run-down of my ideas... - I need to spin off some of the inner classes. There's just too many of them for my liking. Since it'll be in an implementation package, a few extra classes shouldn't matter. - The old implementation uses connection wrappers, where both the wrapper and the wrapped connection have the same API. I'll keep the wrapper concept, but will introduce a different interface for the wrapped one. - Rename Unmanaged*Connection to Operated*Connection. That's the one that will be wrapped. Managed*Connection would be the interface exposed by the wrapper. - HostConfiguration in it's current form is a modifiable implementation of the "routes" I've been discussing in the Wiki. I think the name is a misnomer, but I'll keep it for now in order to get something working a.s.a.p. - I'll put the methods to build a route (tunnelCreated and such) in the connection wrapper and interface. That's where they are now, and it allows for self-managed connections. In other words, classes can handle routing without caring about the connection manager. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
