I do not intent to use it for real production use or anything else serious. Also, probably performance isn't as good as with the mysql or pipe backend, but I I personally felt it's more convenient than the pipe backend for my testing. Sure, you can built a perl script or similar that calls a REST service through the pipe backend, but for all the people that are not perl hackers (including me) a REST service might be a nice thing.
At the end, maybe someone even needs it for applications that do need a very dynamic DNS resolution. Currently its an experiement ... Erik -----Original Message----- From: Jan-Piet Mens [mailto:[email protected]] On Behalf Of Jan-Piet Mens Sent: Mittwoch, 1. Februar 2012 09:10 To: [email protected] Cc: [email protected] Subject: Re: [Pdns-dev] Compiling a custom backend > I would like to develop a custom backend that uses a HTTP rest service > for resolving requests. I'd be interested in hearing the reasons or use-cases for a REST service; care to share? BTW, I assume you know of PowerDNS' PIPE back-end? It could make your life much easier, certainly during the prototyping phase. Just FYI. -JP _______________________________________________ Pdns-dev mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-dev
