Stefano Bagnara wrote:
Serge Knystautas wrote:
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.
Don't know.
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.
Static methods Lookup.setDefaultCache/getDefaultCache can be used to
access the singleton Cache object.
Cache has a setMaxEntries method.
Just an FYI,
Don't know if this is useful so please disregard the noise if the
recommendation is out of place.
You might want to look at using Jdbm for maintaining a single lookup
table backed by a B+Tree as a
disk based cache. It would be ideal for a disk based DNS cache if you
can get the SPI to use it.
Good luck,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
