Register
Blog
New API (read-only) access to DNS data I remember reading many months ago that Henri was working on a new API to access the DNS which would make it easier for web masters to extract read-only data compared to the current procedure. eBay have one which is both very easy to use and powerful - you just issue a single http: command with parameters and receive a response in XML format which you can either use directly (as a RSS Feed) or extract the data from and format as you require. Just wondered what happened to .Tel's new read-only API - is it still being developed and what is the ETA ? Mike Seaton |
See: http://dev.telnic.org/trac/discussion/22/253 I put that out for discussion a while back. |
Henri, of course I would love to see this. Had only I known there was a discussion almost a year ago you would have had my inputs. Mark |
same here - i stopped visiting the dev forum over a year ago.... |
Henri, I hope you didn't think we weren't interested. It's just that nobody here (at least) uses the technical forum. If there was a moderator post here to say there was something important in the technical forum you would have seen more comments. Mark |
Okay fair enough. Let's see where this takes us. Below is the original post (with a caveat at the end): Hello everyone, we're thinking about exposing the .tel DNS data via HTML/JSON. Essentially, a TelProxy? that returns JSON content. As such, I've set up a sample implementation of it at labs.telnic.org which is very much a work in progress at the moment. You can access the API through the following: http://labs.telnic.org/json/[TYPE]?d=[DOMAIN] where TYPE is one of: - all - naptr - txt - loc - ninfo (the header text, but see below) and DOMAIN is the domain that you want to lookup. You can also add '&pretty=1' if you want a nicely formatted JSON string for reading with your eyes. Examples: http://labs.telnic.org/json/loc?d=telnic.tel http://labs.telnic.org/json/all?d=henri.tel&pretty=1 Output: This is where we're looking for feedback. We've attempted to pre-process the stuff that'll be difficult to do in Javascript, while leaving the rest as untouched as possible. So you won't need to deal with regexes or need to extract the labels. Let us know what you think, it's pretty self-explanatory. NOTES: - At this time, if you're looking for the header info, don't request 'ninfo' as the data isn't in the NINFO DNS record, but in the TXT records. So don't use NINFO right now. Also you need to request 'all' or 'txt' if you want the dds string (i.e. the title of the domain/page). - ***If*** this goes in production, we'll try to make it be a "real" RESTful URL in the sense that you'll just need to query:http://henri.tel/json/all to get all the data for henri.tel. But that will depend on the proxy implementation, so we can't guarantee that it will work across the board, at least not initially. |
Henri, this is simple enough for me to write code against in HTML5 and JQuery. Then interface with Google maps and create apps. Working with regex to parse naptr data is a pain as it seems to differ between JS and PHP etc., so having it preprocessed is perfect. Thx Mark |
Henri, was there any additional work on this? Last comment was you'd look at a production implementation. Mark Quote:
|
You shouldt use .deb and plist files At the moment i am working with this files on my iPhone Pimping tweaking and Repimping templates, and the whole system ! |
