On 12/14/2009 03:58 PM, Michael McMahon wrote:
The alternative is to select something O(1)-ish but this can
drastically limit what is possible. Though like I said, for my
purposes if you would allow for host name ("foo.bar.com") and a simple
pattern mechanism ("*.bar.com" but not, say, "foo.*.com
David M. Lloyd wrote:
Responses inline.
On 12/14/2009 12:20 PM, Michael McMahon wrote:
Hi David,
Apologies for missing this when it was suggested originally.
Is there a particular use case you have in mind that requires the
generality provided by the HostMatcher interface? (as opposed to the
Responses inline.
On 12/14/2009 12:20 PM, Michael McMahon wrote:
Hi David,
Apologies for missing this when it was suggested originally.
Is there a particular use case you have in mind that requires the
generality provided by the HostMatcher interface? (as opposed to the
simpler name based appr
Hi David,
Apologies for missing this when it was suggested originally.
Is there a particular use case you have in mind that requires the
generality provided by
the HostMatcher interface? (as opposed to the simpler name based
approach as Chris said)
Presumably, with HostMatcher, you would have
Hi Mark,
I've actually just reproduced this myself on one of our Vista boxes.
I've accepted the bug, 6707289, and will try to determine the root cause.
-Chris.
On 14/12/2009 16:27, Mark Thornton wrote:
On Vista, if you try to find the broadcast address and net prefix length
associated with a
If you want to. I also have another variation where there's a
HttpVirtualHost subclass of HttpHost, which includes a "close()" method
which removes the virtual host. That might make things a little more clear.
Just specifying the host name is OK for some cases, but not for cases where
you wa
On Vista, if you try to find the broadcast address and net prefix length
associated with an IPv4 address (InterfaceAddress.getBroadcast(),
InterfaceAddress.getNetworkPrefixLength()), you get nonsense unless IPv6
is disabled. Bug 6707289 describes the prefix length case.
Workaround: -Djava.net.pre
Hi David,
I looked at the proposal and it looks pretty good, I just have a few
concerns.
HttpHost can be a virtual or real host, and HttpServer is an instance of
a HTTP server running a virtual host. I think this concept is used in
webservers like apache and Sun webserver. I always found it
