This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[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] REST API Problems for DNS measurements with DO and TCP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Quinn
dquinn at ripe.net
Thu Sep 26 14:11:11 CEST 2013
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20130926/9053e300/attachment.html>
- Previous message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
- Next message (by thread): [atlas] REST API Problems for DNS measurements with DO and TCP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]