I see some exciting pipeline-management features landing in new cURL
releases that balance connections to the same hostname. Is there any
interest in extending such support to balancing/fail-over between
multiple A/AAAA records returned for a domain? Since cURL seems to
prefer its own DNS client, it should be possible to expose more DNS
response data to code managing pipelines and the connection pool.

This would be useful for services that connect to multi-master and
replicated systems because it would allow client-based recovery
without an intervening load-balancer. It may also be worthwhile to
support reading SRV-based weights to provide hints to clients about
which servers to prefer for load distribution, bandwidth, or latency
reasons.

My company can sponsor this work if there's interest. We would use it
for our FuseDAV file system client, PHP connections to sets of Solr
replicas, and connections to our distributed internal API from PHP,
Python, node.js, and Ruby.

David
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-04-11