1TODO file for Net::DRI 2Send your wishlist to <netdri@dotandco.com> 3===================================================================== 4 5All 6 * sign the distribution with Module::Signature (1) 7 * add some introspections to be able to know what methods are really available per DRD, instead of throwing an exception ? 8 * implement RFC5105 � ENUM Validation Token Format Definition � 9 * switch from ExtUtils::MakeMaker to Module::Build for better META.yml ? 10 * offer full asynchronous API ? 11 12Net::DRI 13 * IDN support (in a cross registry fashion) with Net-IDN-Tools (1) 14 see also http://www.bsdprojects.net/cgi-bin/archzoom.cgi/tonnerre@bsdprojects.net--2006/Net-DRI--tonnerre--0.81.1--patch-12?log 15 16Net::DRI::DRD 17 * bulk operations (many domains at once) 18 * domain_delete() : try to rename nameservers created in domain about to be deleted 19 * domain_update() / host_update() 20 - try to accomodate (set=>info+add+del, add=>info+set, del=>info+set) 21 - verify not same info in add & del 22 - verify final change is not empty ? 23 * split the module in DRD::Objects::{Domain,Host,Contact,...} + smart loader (like Protocol register_commands) 24 to load the relevant modules based on DRD::object_types() and/or Protocol registered actions and objects 25 26Net::DRI::Protocol::ResultStatus + Net::DRI::Registry 27 * implement the results_* methods added in EPP/Message. Or change API based on wantarray 28 29Net::DRI::DRD::LU 30 * implement startTLS extension ? 31 32Net::DRI::DRD::Nominet 33 * implement DAS and Whois 34 35Net::DRI::Transport::HTTP::* 36 * unify all three modules into one (Net::DRI::Transport::WS ?), taking into account all possible cases 37 * retrofit Transport/SOAP into Transport/HTTP/SOAPLite (1), depending also on previous point 38 39 40 41(1) would be great to have before releasing Net::DRI version 1.0 42