On 4/28/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
dsnjava 2.0.1 currently caches up to 50000 records for each DNS type.
The number is hardcoded so we cannot change it.
We could set our own caches to dnsjava and size them as we prefer.
We should also remove the cache done in the DNSServer: why should we add
our own cache lookup (on dnsjava objects) when dnsjava already support this?
On the InetAddress side, I see that dnsjava is an SPI for dns lookups.
Adding "sun.net.spi.nameservice.provider.1=dns,dnsjava" we would make
all the dns calls to use dnsjava the way we configured it.
Should we use the spi approach or try to propagate the
DNSServer.staticMethods usage we currenlty use sometimes??
I thought we had already gone the spi approach, or at least had
considered it at one point. I thought there was some issue with
different results, but I don't remember any specifics.
In terms of caching, is there a way we can make this configurable,
i.e., how does the dnsjava Cache get instantiated? Is it static, or
is there a singleton we create somewhere to handle this? If we
instantiate the singleton in the DNSServer, we could expose the cache
impl or limitations from the dnsserver conf block. I wonder how the
spi would instantiate it.
--
Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
