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