Home | History | Annotate | Download | only in mDNSCore

Lines Matching full:service

18    If you're building an application that uses DNS Service Discovery
39 independent client processes communicate their DNS Service Discovery
156 kDNSType_WKS, // 11 Well-known-service
178 kDNSType_SRV, // 33 Service record
632 // -- Shared Resource Records are used for DNS-SD service PTRs
659 // Shared No No Yes e.g. Service PTR record
1108 // Unless otherwise noted, states may apply to either independent record registrations or service registrations
1247 mDNSBool SRVChanged; // temporarily deregistered service because its SRV target or port changed
1383 // it is just a convenience structure to group together the records that make up a standard service
1387 // * the basic PTR/SRV/TXT triplet used to represent any DNS-SD service
1388 // * the "_services" PTR record for service enumeration
1390 // * the optional list of additional records attached to the service set (e.g. iChat pictures)
1401 ExtraResourceRecord *Extras; // Optional list of extra AuthRecords attached to this service registration
1483 AuthRecord AutoTunnelService; // Service record (possibly NAT-Mapped) of IKE daemon implementing tunnel endpoint
1594 mDNSAddr ip; // Remote (destination) IP address where this service can be accessed
1595 mDNSIPPort port; // Port where this service can be accessed
1631 ZoneService ZoneService; // Which service we're seeking for this zone (update, query, or LLQ)
1886 DNSQuestion ReverseMap; // Reverse-map query to find static hostname for service target
2086 // 2. A proxy-registration service, that advertises services being offered by other machines, and takes
2088 // In principle, a proxy-like registration service could manually create address records for its own machine too,
2184 // mDNS_RegisterService is a single call to register the set of resource records associated with a given named service.
2187 // to find the IP address, port number, and demultiplexing information for a given named service.
2189 // found. After the service is resolved, the client should call mDNS_StopResolveService to complete the transaction.
2192 // mDNS_AddRecordToService adds an additional record to a Service Record Set. This record may be deregistered
2193 // via mDNS_RemoveRecordFromService, or by deregistering the service. mDNS_RemoveRecordFromService is passed a
2203 // of one or more domains that should be offered to the user as choices for where they may register their service,
2761 // Sleep Proxy Servers are advertised using a structured service name, consisting of four
2779 // installed for the express purpose of providing Sleep Proxy Service.
2810 // reasonable candidate for providing Sleep Proxy Service e.g. Apple TV,