Salut,
Oleksiy Stashok wrote:
> Hi Hubert,
>
>>
>> I'm was recently looking at GWS and its HTTPS support.
>> I found out that user can start GWS configured to serve HTTPS without
>> SSLConfig.
>> This renders service unusable.
> We can try to use some "default" SSLConfig, which reads SSL
> configuration from System properties.
>
>> What do you think of deprecating constructor with boolean secure
>> parameter and creating one that would require SSLConfig?
> IMHO it could be even more clear, if we can split GrizzlyWebServer
> implementation into two: Secure and non-Secure.
Hum :-) I would think it is much simpler to have a single entry point. A
default SSLConfig is probably what we want (JDK 7 will add that features).
> But because of backwards compatibility, not sure we will want to do that.
And easy of use :-)
>
> As for deprecating/adding constructors to GrizzlyWebServer, there are a
> lot of them already, so we have to avoid doing mess there :)
Can't agree more :-)
A+
-- Jeanfrancois
>
> WBR,
> Alexey.
>
>>
>> Cheers,
>> Hubert.
>