public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "JOSHI, RAHUL" <rahulj@hpe.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: RE: Having TTL of resolved IP addresses in 'getaddrinfo' or 'getaddrinfo_a'
Date: Wed, 5 May 2021 08:33:17 +0000	[thread overview]
Message-ID: <CS1PR8401MB0502BBD6434701E2E8DBED87C0599@CS1PR8401MB0502.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CS1PR8401MB0502958E8F2E90F0AC840759C05B9@CS1PR8401MB0502.NAMPRD84.PROD.OUTLOOK.COM>



From: JOSHI, RAHUL
Sent: Wednesday, May 05, 2021 1:57 PM
To: 'libc-help@sourceware.org' <libc-help@sourceware.org>
Subject: RE: Having TTL of resolved IP addresses in 'getaddrinfo' or 'getaddrinfo_a'

Hi all, is there any update on this??

Thanks,
Rahul

From: JOSHI, RAHUL
Sent: Monday, May 03, 2021 11:30 AM
To: libc-help@sourceware.org<mailto:libc-help@sourceware.org>
Subject: Having TTL of resolved IP addresses in 'getaddrinfo' or 'getaddrinfo_a'

Hi all, in current implementation of 'getaddrinfo' or 'getaddrinfo_a' , the TTL(expiry time) of resolved IP addresses isn't provided. Is there any alternate API in libc which will provide resolved IP addresses along with TTL??

If no, what needs to be done to get the resolved addresses along with TTL??

Thanks,
Rahul

  parent reply	other threads:[~2021-05-05  8:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03  5:59 JOSHI, RAHUL
2021-05-05  8:27 ` JOSHI, RAHUL
2021-05-05  8:33 ` JOSHI, RAHUL [this message]
2021-05-05  8:39 ` Florian Weimer
     [not found]   ` <CS1PR8401MB050236FE63C077687BC1C1D7C0599@CS1PR8401MB0502.NAMPRD84.PROD.OUTLOOK.COM>
2021-05-05  9:41     ` JOSHI, RAHUL
2021-05-05 12:27     ` JOSHI, RAHUL
2021-05-06  8:05     ` JOSHI, RAHUL
2021-05-06  9:20       ` Florian Weimer
2021-05-17 11:13 JOSHI, RAHUL
2021-05-17 11:16 ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CS1PR8401MB0502BBD6434701E2E8DBED87C0599@CS1PR8401MB0502.NAMPRD84.PROD.OUTLOOK.COM \
    --to=rahulj@hpe.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-help@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).