Peter Bourgon 8602132ab6 Move concurrency from resolve to HTTP GET ...

- Process DNS resolution serially
- Process up to 10 HTTP GET (for app ID) concurrently

More than 10 concurrent GET requests will block on the semaphore. This
will cause the staticResolver.resolve method to block, which is probably
fine: it will just delay the next resolve loop, currently at 1m
intervals.

To make this a little bit more robust, I've also added a fastClient for
app ID resolution, with a timeout (total, including connect, request,
and response) of 5s.

2015-09-24 16:56:37 +02:00

..

docker

Extend docker module testing.

2015-09-24 05:30:40 +00:00

endpoint

Review feedback

2015-09-24 03:07:20 +00:00

host

Audit uses to Topology.Nodes, use AddNode where appropriate.

2015-09-23 07:36:51 +00:00

overlay

Refactor MultiPublisher

2015-09-24 16:11:55 +02:00

process

Use AddNode when adding nodes to the topology, such that the get merged with any existing node that might be there.

2015-09-15 10:02:58 +00:00

hostname.go

Remove old references

2015-05-19 10:05:03 +00:00

instrumentation.go

Duplicate endpoints in the endpoint topology to account for NAT mapping.

2015-06-23 10:33:06 +00:00

main.go

Refactor MultiPublisher

2015-09-24 16:11:55 +02:00

resolver_test.go

Move concurrency from resolve to HTTP GET

2015-09-24 16:56:37 +02:00

resolver.go

Move concurrency from resolve to HTTP GET

2015-09-24 16:56:37 +02:00

tag_report_test.go

Audit uses to Topology.Nodes, use AddNode where appropriate.

2015-09-23 07:36:51 +00:00

tag_report.go

Audit uses to Topology.Nodes, use AddNode where appropriate.

2015-09-23 07:36:51 +00:00