HsDNS -- asynchronous DNS resolver
On top of the GNU adns library, I have implemented a pretty simple-to-use DNS resolver, which hides the concurrency from the user through the use of MVars. I thought, maybe someone found this useful. You can get the source code at: http://cryp.to/hsdns/ Peter
On Thu, Jun 17, 2004 at 02:20:49PM +0200, Peter Simons wrote:
On top of the GNU adns library, I have implemented a pretty simple-to-use DNS resolver, which hides the concurrency from the user through the use of MVars. I thought, maybe someone found this useful. You can get the source code at:
You stole my project's name! Oh, well, I guess I should have released it, now I can't complain :( BTW, my library is pure Haskell. In a month or two I'll try to replace Parsec (yes, I used Parsec to decode DNS packages :) with my UArrayParser, implement full domain name resolution algorithm, think of another name, and release it. Best regards, Tom -- .signature: Too many levels of symbolic links
Tomasz Zielonka writes:
You stole my project's name!
I have to admit that I am uncertain whether you are kidding or whether this is a serious complaint, but in case of the latter, I'll change the name to HsADNS or whatever. I can't say I am emotionally invested in how this thing is called, so if it's important to you ... let me know and I'll change it. Peter
On Fri, Jun 18, 2004 at 11:17:52AM +0200, Peter Simons wrote:
Tomasz Zielonka writes:
You stole my project's name!
I have to admit that I am uncertain whether you are kidding or whether this is a serious complaint, but in case of the latter, I'll change the name to HsADNS or whatever. I can't say I am emotionally invested in how this thing is called, so if it's important to you ... let me know and I'll change it.
I am sorry, I forgot the smiley. A bit late, but here it is: ;) Please, keep the current name. Maybe we could have two implementations behind one interface? Best regards, Tom -- .signature: Too many levels of symbolic links
Tomasz Zielonka writes:
Maybe we could have two implementations behind one interface?
It sure sounds nice, but the problem is that the API is basically nothing more than the data types used to represent DNS queries and answers. My API has just one single function: query. So having the same API comes down to having the same data types in both of our modules ... I don't know whether this is feasible. We could have a common DNS.Datagram module, maybe, which both libraries could use? Also, I am not entirely free to choose the data types I use, because I have to marshal them (efficiently) for ADNS. If it can be done, I am all for it. But I probably wouldn't want to invest too much time into the problem. Once your implementation is stable, I think most people will prefer the pure Haskell version anyway and stick with yours. I thought of HsDNS as an interim solution anyway, it's just a solution that works _now_. Peter
participants (2)
-
Peter Simons -
Tomasz Zielonka