commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Savarese (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NET-163) [contribution] DNS utils
Date Wed, 18 Jul 2007 17:48:06 GMT

    [ https://issues.apache.org/jira/browse/NET-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513653
] 

Daniel Savarese commented on NET-163:
-------------------------------------

> Attached classes provide evident API for receiving information from DNS serv
>er as wrapper for JNDI DNS SP. Also these classes provide necessary additional

I have yet to look at the code, but I think it's important to remember that
Commons Net has all along been an implementation of protocols at the lowest
level and not a wrapper library.  Wrapping JNDI seems out of scope to me
because Commons Net is supposed to be the sort of thing that sits a layer
underneath JNDI (e.g., a JNDI implementation would use a Commons Net
DNS implementation; not the other way around).  At any rate, that's my
initial reaction.

Also, any substantial code contributions have to go through the proper
paperwork.  And we need to start pulling in people who contribute code
as committers instead of letting them dump off a hefty chunk of code
and disappearing as has happened a couple of times (although in at
least one case, I think the contributor became a committer).  Not that
I've been a particularly active contributor of late ...

At any rate, just a couple of thoughts to consider before accepting
more Commons Net contributions.

> [contribution] DNS utils
> ------------------------
>
>                 Key: NET-163
>                 URL: https://issues.apache.org/jira/browse/NET-163
>             Project: Commons Net
>          Issue Type: New Feature
>            Reporter: Nikolay Chugunov
>         Attachments: dnsutils.zip
>
>
> Hi all,
> I developed DNS methods for resolving IP address by host name and vice verse; receiving
mail exchange and authoritative name servers for domain; and receiving other information about
domain from DNS server.
> JDK provides above functionality in JNDI DNS service provider [1]. But JNDI technology
is too abstract and obfuscates communication with DNS servers, which leads to users don't
use JNDI DNS SP.
> Attached classes provide evident API for receiving information from DNS server as wrapper
for JNDI DNS SP. Also these classes provide necessary additional parsing of answers.
> Examples how to use created API can be found in DNSClientTest unit test. This library
requires only JDK and JUnit to run the test.
> [1] http://java.sun.com/javase/6/docs/technotes/guides/jndi/jndi-dns.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message