directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1930) DhcpOptions not extensible
Date Thu, 12 Dec 2013 12:43:07 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846276#comment-13846276
] 

Emmanuel Lecharny commented on DIRSERVER-1930:
----------------------------------------------

That's pretty simple. Bacj in 2005, when the project started, it was thought as being a protocol
layer built on top of a backend. The backend is BTree based, and various protocols can be
built on top of it. Typically, we currently support LDAP and Kerberos.

Some experiment have been conducted to prove that some other protocols can be easily implemented.
Here is a list of what we have worked on back then :
- DHCP
- DNS
- NTP

NTP protocol is supported, but in fact, it's really a facade, there is no meat in it. DNS
and DHCP are also implemented, probably in a better state, but it's really far from being
perfect.

At this point, you should consider that the protocol part (ie, messages encoding and decoding)
is supported, and the data are stored into the backed. In the middle, there is little and
this need some love we can't currently provide.

If you think you can help in one of these areas, you are very welcome. The best is to povide
patches, thatt you can attach to JIRAs like this one (or other more specific ones). 

It's really up to you, but be sure we will be around to help you during your learning curve.
This is how OSS projects work, all in all !

> DhcpOptions not extensible
> --------------------------
>
>                 Key: DIRSERVER-1930
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1930
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: dhcp
>            Reporter: Shevek
>
> It is impossible to add my own DhcpOption types, due to the fixed and private static
encapsulation in DhcpOption. Also, the option set isn't even complete enough for practical
use.
> This method:
>     public static int getTagByClass( Class c )
>     {
>         return ( ( Integer ) CODE_BY_CLASS.get( c ) ).intValue();
>     }
> will NPE given an option class which isn't privately registered.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message