[atlas] REST API Problems for DNS measurements with DO and TCP
- Previous message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
- Next message (by thread): [atlas] Replacing "ping RRDs" with "zoomable ping graphs"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.mailinglists at pernau.at
Thu Sep 26 15:46:08 CEST 2013
On 26.09.2013 14:11, Daniel Quinn wrote: > On Thu 26 Sep 2013 11:08:28 AM CEST, Klaus Darilion wrote: > > IMO, this should be consistent too. > > You know what, you‘re totally right. I had a rough time setting this all > up in the beginning and this one slipped through the cracks. I’ve now > gone ahead and made the change to the API to use |protocol| instead of > |use_tcp|. New appropriate values include |TCP| or |UDP|. *Using the old > method will no longer work*, and the documentation has been > appropriately updated. > > Thanks for catching this, and my apologies to those of you who may be > using |use_tcp|. I'm sure you can all agree though that consistency is > best for something like this. I tested it and it works now as you describe. Thanks Klaus
- Previous message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
- Next message (by thread): [atlas] Replacing "ping RRDs" with "zoomable ping graphs"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]