| /external/autotest/client/common_lib/cros/ |
| D | dbus_send.py | 116 responder = match.group(2)
121 return DBusSendResult(sender=sender, responder=responder, response=ret_val)
|
| /external/nanohttpd/nanolets/src/main/java/fi/iki/elonen/router/ |
| D | RouterNanoHTTPD.java | 375 UriResponder responder = (UriResponder) object; in process() local
378 return responder.get(this, urlParams, session); in process()
380 return responder.post(this, urlParams, session); in process()
382 return responder.put(this, urlParams, session); in process()
384 return responder.delete(this, urlParams, session); in process()
386 … return responder.other(session.getMethod().toString(), this, urlParams, session); in process()
|
| /external/iputils/ |
| D | rdisc.c | 189 int responder; variable
318 responder = 1; in main()
376 if (responder) in main()
390 if (responder) in main()
406 if (solicit && responder) { in main()
430 if (responder) in main()
507 if (responder && left_until_advertise <= 0) { in timer()
745 if (responder) in pr_pack()
834 if (!responder) in pr_pack()
965 if (responder) { in finish()
|
| D | RELNOTES | 143 rdisc: Make rdisc with responder support if configured.
|
| /external/mdnsresponder/mDNSPosix/ |
| D | ReadMe.txt | 211 To continue with the test you should start the responder in another
216 This will start the responder and tell it to advertise a AppleShare
224 Back in the responder window you can quit the responder cleanly using
231 As the responder quits it will multicast that the "Foo" service is
|
| /external/ipsec-tools/src/racoon/samples/ |
| D | racoon.conf.sample | 42 # the configuration could makes racoon (as a responder)
|
| /external/avahi/specs/ |
| D | draft-cheshire-dnsext-multicastdns-05.txt | 222 single responder, and at most one responder should respond to any
224 set, a responder MUST probe to verify that no other responder
467 in the case of overlayed subnets. If a responder receives a query
469 source address not apparently on the same subnet as the responder,
472 responder SHOULD elect to respond by multicast anyway, since it can
709 responder SHOULD usually respond with a unicast packet directed back
710 to the querier. If the responder has not multicast that record
711 recently (within one quarter of its TTL), then the responder SHOULD
757 RR TTL as known by the Multicast DNS Responder, the responder MUST
862 that the responder determines than an unsolicited announcement is
[all …]
|
| D | draft-cheshire-dnsext-multicastdns-06.txt | 198 or ownership of a single responder, and it is expected that at most
199 one responder should respond to a query for that name, rrtype, and
201 a responder MUST probe to verify that no other responder already
204 have more than one responder answering for a particular "unique"
481 in the case of overlayed subnets. If a responder receives a query
483 source address not apparently on the same subnet as the responder,
486 responder SHOULD elect to respond by multicast anyway, since it can
750 responder SHOULD usually respond with a unicast packet directed back
751 to the querier. If the responder has not multicast that record
759 recently (within one quarter of its TTL), then the responder SHOULD
[all …]
|
| D | draft-cheshire-dnsext-multicastdns-04.txt | 662 responder SHOULD usually respond with a unicast packet directed back
663 to the querier. If the responder has not multicast that record
664 recently (within one quarter of its TTL), then the responder SHOULD
717 RR TTL as known by the Multicast DNS Responder, the responder MUST
847 believe that it will be the only responder on the link with a
1841 "stuartcheshire.local", then a responder having an address record
1848 programmatically-generated CNAME records. For example, if a responder
1851 removed, then the responder may issue a response containing two
1959 Known Answer records may be following shortly. A responder MAY choose
|
| D | draft-cheshire-dnsext-multicastdns-03.txt | 662 responder SHOULD usually respond with a unicast packet directed back
663 to the querier. If the responder has not multicast that record
664 recently (within one quarter of its TTL), then the responder SHOULD
717 RR TTL as known by the Multicast DNS Responder, the responder MUST
847 believe that it will be the only responder on the link with a
1841 "stuartcheshire.local", then a responder having an address record
1848 programmatically-generated CNAME records. For example, if a responder
1851 removed, then the responder may issue a response containing two
1959 Known Answer records may be following shortly. A responder MAY choose
|
| D | draft-cheshire-dnsext-dns-sd-02.txt | 1355 server/responder SHOULD include the following additional records:
1365 server/responder SHOULD include the following additional records:
|
| D | draft-cheshire-dnsext-dns-sd-03.txt | 1437 server/responder SHOULD include the following additional records:
1458 server/responder SHOULD include the following additional records:
|
| D | draft-cheshire-dnsext-dns-sd-04.txt | 1495 server/responder SHOULD include the following additional records:
1516 server/responder SHOULD include the following additional records:
|
| /external/ipsec-tools/src/racoon/ |
| D | TODO | 79 o responder policy and initiator policy should be separated.
|
| /external/bouncycastle/bcprov/src/main/java/org/bouncycastle/x509/ |
| D | CertPathReviewerMessages.properties | 400 CertPathReviewer.ocspLocation.title = OCSP responder location
401 CertPathReviewer.ocspLocation.text = OCSP responder location: {0}.
402 CertPathReviewer.ocspLocation.summary = OCSP responder location: {0}.
403 CertPathReviewer.ocspLocation.details = OCSP responder location: {0}.
|
| /external/iputils/doc/ |
| D | rdisc.sgml | 64 Or, <command/rdisc/ can act as responder, if compiled with -DRDISC_SERVER.
|
| /external/wpa_supplicant_8/hs20/server/ |
| D | hs20-osu-server.txt | 212 ./ocsp-responder.sh&
|
| /external/curl/lib/vtls/ |
| D | openssl.c | 1326 X509 *responder = sk_X509_value(br->certs, sk_X509_num(br->certs) - 1); in verifystatus() local
1331 if(X509_check_issued(issuer, responder) == X509_V_OK) { in verifystatus()
|
| /external/ipsec-tools/ |
| D | ChangeLog | 727 does not know yet if the responder can handle IKE frag. However, in
|
| /external/wpa_supplicant_8/wpa_supplicant/ |
| D | README-P2P | 248 This command sends a provision discovery response from responder side.
|