Salut,
Oleksiy Stashok wrote:
> Hi,
>
>> In domain.xml, an admin can define which address to bind the
>> http-listener to (defaults to "0.0.0.0" iirc). There's no address
>> currently in the DTD (though adding that is easy enough). In
>> network-listener, there is the "host" attribute which stands a pretty
>> chance of being what I want. Is that intended to be the physical
>> address? If so, I think we should rename it or at the least update
>> the comments.
> Hmm. Socket API uses both names in the same way. I'm ok to change this
> to address.
>
>> There also appears to be no grizzly counterpart suitable for
>> converting access-log entries over to grizzly. That's assuming, of
>> course, we want to do the logging in grizzly and not keep it in
>> glassfish, but I think it makes sense for grizzly to deal with it
>> especially with port unification looming...
> Think we planned to keep access-log with WebContainer related config,
> not Grizzly.
Yes, as access log is implemented a Valve in WebContainer. But it may
make sense to implement it directly in Grizzly performance wise...but we
don't have time I guess.
A+
- Jeanfrancois
>
> Thanks.
>
> WBR,
> Alexey.
>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>