<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br></div><div>Folk,</div><div><br></div><div>First, I am very grateful to Dick who introduced a lot of quality improvements in the Net::DNS internals, developments that caused some changes to the API. That said, I am sensitive to problems that are caused by changing APIs. The introduction of the @-sign in the SOA rname field is one of them. </div><div><br></div><div>What I would like to now is whether there are other places where you experienced pain. Please, be so kind to report that as a reply to this thread so that we have an inventory of pain-points. As an aid you can refer to the list attached. (Previously distributed to this lis in a thread with subject "<span style="font-size: 12px; ">List of API changes in versions after 0.68?"). Please do not use this inventory as a wish list for changes you would like to see in Net::DNS in general. Just focus on things that changes after .68 and that caused serious problems.</span></div><div><div><br></div></div><div><br></div><div>In about a week or two we'll go over the list and propose actions.</div><div><br></div><div>--Olaf</div><div><br></div><div>PS: From an NLnet Labs perspective we try to moderate the development of Net::DNS much more than we try to lead it: I see Net::DNS much more as a community effort and we are very liberal in sucking up contributions. </div><div><br></div><div>PPS: The trend in contributions is that in general the architecture becomes cleaner and more efficient and provides a clean and less error prone access to write and read DNS from the wire, however that may be at the expense of the ability to hack around. </div><div><br></div><div><br></div><div>PPS: I regret not having set up this mailing list before.</div><div><br></div><div><br></div><div><br></div><div><br></div><div></div></body></html>