I don't know enough about the DNS protocol, but are there limitations. This seems like a weird way to do it... Are we just doing it to be novel, or I don't see why a typical webserver serving JSON (pretty well tested) set up isn't good enough.
On Wed, Jun 2, 2010 at 9:20 PM, Jeremy Orem <[email protected]> wrote: > It would be nice to, also, have the ability to also point it at a JSON > file over HTTP: > > * other web services could easily pull the data > * it's easier, in my opinion, to throw some JSON up on a webserver > than maintain TXT records on a DNS server > * python has built-in libraries to do this > > -Jeremy > > On Wed, Jun 2, 2010 at 9:11 PM, Jerry Chen <[email protected]> wrote: > > > > > > On Jun 2, 2010, at 11:08 PM, Tom Davis wrote: > > > >>> IMHO I think it would be awesome to not have another dependency and > make a really specialized DNS TXT lookup module. > >>> > >>> But I suppose I should back that up with a patch first! > >>> > >>> Jerry > >> > >> Forgive me, but what is the big issue with dependencies? Why spend > valuable time writing and debugging a DNS module when dependencies don't > effect the way 99% of people would install the libcloud package? Even after > the drawn out anti-zope.interface argument, I still don't get it. If a > module is well-tested, stable, and available via the cheese shop, there's no > downside to using it (from my perspective, anyway). > > > > Indeed, I took a look at implementing TXT lookups and it's non-trivial. > > > > As for Zope, it didn't seem like it was bringing much value. > > > > Jerry > -- Dan Di Spaltro cloudkick.com co-founder (408) 603-9137
