Hi Oleg,
>> I'm open to suggestions, of course. Maybe an
>> enum for PLAIN, TUNNELLED, TUNNELLED_AND_LAYERED
>> plus an extra boolean for the secure flag?
>
> Something as trivial as that should already be an improvement in my
> opinion:
>
> enum ConnSecurity {
> PLAIN,
> SECURE
> }
The security flag has many incarnations. There's one in
the route, one on the connection, it needs to be checked
in HttpCookie too. If we introduce an enum for that, it
should not be simply because of the route.
> enum ConnTunneling {
> DIRECT,
> TUNNELED
> }
>
> enum ConnLayering {
> SIMPLE,
> LAYERED
> }
I have begun to like the idea of joining these two to
eliminiate the invalid state. I'll open an issue.
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
