Difference between revisions of "Why Asynchronous DNS"
(cleanup, added xrefs to RFC 3263 and the svn repository)
|Line 1:||Line 1:|
. in ..
It is impossible to know ahead of time how long a
It is impossible to know ahead of time how long a query will take. If the client library is synchronouscare must be taken in the application to avoid blocking while a result is being retrieved. There are two methods of dealing with this problem: asynchronous blah, blah, blah
Revision as of 12:42, 9 February 2006
SIP clients and servers can use DNS to resolve URIs for locating next hops. Details are covered in RFC 3263.
ReSIProcate uses a forked version of the ares asynchronous DNS library originally from MIT. This forked version is located in the contrib subdirectory of reSIProcate's svn repository. The reSIProcate version offers the following over the MIT version:
- numerous bug fixes, particularly on win32 architectures
- support of IPV6