Hi Oleg, > Here's my take on the matter. Proxy chaining is only relevant for large > corporations with complex security requirements and regulations.
I agree. > Those > people can usually afford to task a software engineer or two with > writing a custom component to meet their specific requirements. You > probably should not spend your time writing and testing all this > non-trivial code (unless you feel like doing so, of course). Surely not testing it (extensively). > Support for > proxy chaining should probably donated to the project by an external > (most likely commercial) entity. All we have to ensure is that HttpRoute > is flexible enough to represent a chain of proxies. That's it. As discussed a few weeks ago, I don't want to open up HttpRoute for custom extensions. So I'm looking for a way to represent proxy chains in it by default. This affects the behavior and therefore the description of some of the existing methods, that's why I wanted to check back before starting to hack. RouteTracker needs to be kept in sync with HttpRoute. We could leave the RouteDirector without proxy chain support. I don't think it's much effort to add it, as long as all proxies are plain HTTP, and only the last one operates without a tunnel. If I should be wrong in that point, I'll stop right there. The RouteDirector is open for extension, so layering of sockets to proxies rather than end-to-end is definitely a customization. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
