Menu
▾
▴
Re: Re: [Epp-rtk-devel] IDN 4 java
|
From: Jens-Uwe G. <ju...@sc...> - 2003-12-01 20:05:49
|
Dear Daniel, you should avoid sending HTML-mails, it's very hard to read for the people subscribed to the daily-overview on the EPP-mailing-list (like myself ;) ... and it's also not looking good in the Mailing-list- archives on sourceforge: http://sourceforge.net/mailarchive/message.php?msg_id=6647800 Kind regards, Jens-Uwe Gaspar Daniel Manley <dm...@li...> wrote: > Date: Fri, 28 Nov 2003 16:38:43 -0500 > From: Daniel Manley <dm...@li...> > To: epp...@li... > Subject: Re: [Epp-rtk-devel] IDN 4 java > > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > <html> > <head> > <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> > <title></title> > </head> > <body text="#000000" bgcolor="#ffffff"> > Thanks, Jens-Uwe, That's in line with other feedback I've gotten, plus > my own humble opinion.<br> > <br> > How do people feel about a provider-flexible wrapper around IDN code? > Something to make it super-easy to do this kind of thing:<br> > <br> > domain_create_req.setName(rtk_idn_provider.encode(domain_name));<br> > <br> > hopefully to hide all of the messy integer and byte array stuff and so > on -- again, completely by-passable for those who have stuff already > set up. Is it overkill on design?<br> > <br> > Dan<br> > <br> > <br> > Jens-Uwe Gaspar пишет:<br> > <blockquote type="cite" cite="mid...@sc..."> > <pre wrap="">Dear Daniel, > > Daniel Manley <a class="moz-txt-link-rfc2396E" href="mailto:dm...@li..."><dm...@li...></a> wrote: > </pre> > <blockquote type="cite"> > <pre wrap="">... > Date: Mon, 24 Nov 2003 12:16:09 -0500 > From: Daniel Manley <a class="moz-txt-link-rfc2396E" href="mailto:dm...@li..."><dm...@li...></a> > To: <a class="moz-txt-link-abbreviated" href="mailto:epp...@li...">epp...@li...</a> > Subject: [Epp-rtk-devel] IDN 4 java > > hey guys and gals, > > I'm would like to get a feel for people's choice on IDN code for the > RTK. Since .info will be releasing German IDN, I'm getting ready to > work on this. Without knowing any licensing details in detail, it seems > like there are a few choices for proceeding... > > 1) write something from scratch in 100% java --- no nonsense solution, > 100% cross-platform, no worries for Windows plaformers (with respect to > choice #2) > 2) use Java wrappers to libidn --- let's us use the same libraries for > the C++ code, good for consistency, but mean compiling gnu/linux C code > for windows users, something to consider for 100% java shops > 3) use Verisign's IDN SDK (under BSD license -- is that compatible with > RTK which is under LGPL?) > 4) others? especially opensource and 100% java? > > what's the easiest to use for a registrar using the RTK? I was thinking > that this was going to be an extension/add-on package rather than coded > into the main RTK -- nameprep first, then pass to the RTK domain:check, > domain:create, etc -- making its integration and usage optional for > those who already use a different favourite package or who don't want to > offer IDNs. Also, keeps the RTK releases stable while a separate idn > package might go through multiple bug fix or enhancement releases. > Thoughts? Suggestions? > </pre> > </blockquote> > <pre wrap=""><!----> > Keeping the IDN-stuff in a separate package is a good idea, > so that the clients (registrars) can use whatever they prefer > (we for example are using Verisign's IDN SDK for quite a while now). > > --- > Beside of that, a registry can have its own policy what to expect > to come out of the data-protocol as domainname: > > a) IDN (Unicode domainname), or > b) namepreped/ace-encoded (or whatever encoded) domainname > > The RTK should be able to deal with both cases and simple passing > through the specified domainname (whatever coding is used). > > Kind regards, > > Jens-Uwe Gaspar >... ________________________________________________________________________ Jens-Uwe Gaspar Schlund + Partner AG E-Mail: ju...@sc... Brauerstr. 48 Tel. +49-721-91374-50 76135 Karlsruhe, Germany Fax +49-721-91374-20 http://www.schlund.de |