libasyncns

I Use This!

Inactive

Analyzed about 23 hours ago. based on code collected 1 day ago.

Project Summary

libasyncns is a C library for Linux/Unix for executing name service queries asynchronously. It is an asynchronous wrapper around getaddrinfo(3), getnameinfo(3), res_query(3) and res_search(3) from libc and libresolv.

In contrast to GNU's asynchronous name resolving API getaddrinfo_a(), libasyncns does not make use of UNIX signals for reporting completion of name queries. Instead, the API exports a standard UNIX file descriptor which may be integerated cleanly into custom main loops.

In contrast to asynchronous DNS resolving libraries like libdenise, skadns, adns, libasyncns is just an asynchronous wrapper around the libc's synchronous getaddrinfo() API, which has the advantage of allowing name resolution using techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name Service Switch) modules. libasyncns is compatible with IPv6 if the underlying libc is.

In a Nutshell, libasyncns...

...
has had 118 commits made by 3 contributors
representing 1,978 lines of code
...
is mostly written in C
with a low number of source code comments
...
has a codebase with a long source history
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in January, 2005
ending with its most recent commit over 14 years ago

Quick Reference

Project Links:

Homepage

Code Locations:

git://git.0pointer.de/libasyncns

Similar Projects:

Managers:

Become the first manager for libasyncns

Licenses

MIT

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Use Patent Claims

Forbidden

Sub-License

Hold Liable

Required

Distribute Original

Disclose Source

Include Copyright

State Changes

Include License

Include Install Instructions

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
use of OSS increased in 65% of companies in 2016
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
...
in 2016, 47% of companies did not have formal process in place to track OS code
...
data presented on the Open Hub is available through our API