Re: Possibility to extend the Zone class

[Lucas F. <li...@sa...>]

Hello Brian,

Thanks for you prompt answer.

I agree that introducing an interface may break backwards
compatibility. But a way to allow users to define their own Zone
mechanism would be great. In the end, I had to alter the visibility of
several fields in the Zone class and the SetResponse class.

If you can think of another solution, I am willing to spend a few
cycles to help.

Regards,

Lucas

On Wed, Oct 12, 2011 at 16:09, Brian Wellington <bwe...@xb...> wrote:
>
> On Oct 12, 2011, at 11:49 AM, Lucas Ferreira wrote:
>
>> Hello,
>>
>> I am working on a project based on dnsjava (actually, I am trying to
>> extend Eagle DNS) and need to publish a zone which is too big too fit
>> in memory, so I need to extend the Zone class.
>>
>> While woking on this, I am having problems because the Zone
>> findRecords method must return a SetResponse object. Unfortunately,
>> the SetResponse constructors and set methods are only available inside
>> the org.xbill.DNS package, which makes it impossible to extend the
>> Zone class without altering the dnsjava jar file.
>>
>> So, I have a couple of questions/suggestions:
>>
>> 1. Is it possible to make dnsjava more extensible by providing Zone as
>> an interface, so users may provide their own Zone implementations?
>
> It's certainly possible, but it would break backwards compatibility, which is a bad thing.
>
>> 2. Is it possible to make the SetResponsible constructors and setters
>> available to external classes?
>
> Possibly, but the external API would need some cleaning up first.
>
> Brian



-- 
Homo sapiens non urinat in ventum.