Lines Matching refs:service
38 * Bonjour allows you to register a network service, such as a
40 * for by service type and domain. Using Bonjour, applications can
43 * necessary to access a particular service.
52 * networks without requiring the service or the application to support
65 * ("system service" on Windows) meets some required minimum functionality level.
195 * by renaming the service. NoAutoRename overrides this behavior - with this
197 * is only valid if a name is explicitly specified when registering a service
253 /* A service registered with the NonBrowsable flag set can be resolved using
374 * class for packets that service the request.
451 * This flag is meaningful only in DNSServiceRegister. When set, the service will not be registered
562 kDNSServiceType_WKS = 11, /* Well known service. */
661 /* Maximum length, in bytes, of a service name represented as a */
694 * As DNS-SD becomes more popular, rich-text domains for service discovery will
699 * _service._udp, where the "service" part is 1-15 characters, which may be
713 * Suppose you have an service called "Dr. Smith\Dr. Johnson", of type "_ftp._tcp"
715 * The full (escaped) DNS name of this service's SRV record would be:
737 * a service, then that service will be found *only* by other local clients
740 * If a client has a 'private' service, accessible only to other processes
741 * running on the same machine, this allows the client to advertise that service
742 * in a way such that it does not inadvertently appear in service lists on
748 * accomplish this by inspecting the interfaceIndex of each service reported
764 * set, because resolving a P2P service may create and/or enable an interface whose
766 * interface via which the service can be accessed.
770 * to include P2P. In this case, if a service instance or the record being queried
806 * if the daemon (or "system service" on Windows) is not running.
929 * added to the service via DNSServiceAddRecord(), the DNSRecordRef created by the Add() call
1039 /* Register a service that is discovered via Browse() and Resolve() calls.
1047 * DNS-SD is in use, it is possible for a single service to get
1054 * the service registration by calling DNSServiceRefDeallocate(ref);
1061 * name: The service name registered (if the application did not specify a name in
1064 * regtype: The type of service registered, as it was passed to the callout.
1066 * domain: The domain on which the service was registered (if the application did not
1068 * on which the service was registered).
1093 * interfaceIndex: If non-zero, specifies the interface on which to register the service
1101 * name: If non-NULL, specifies the service name to be registered.
1109 * regtype: The service type followed by the protocol, separated by a dot
1110 * (e.g. "_ftp._tcp"). The service type must be an underscore, followed
1112 * The transport protocol must be "_tcp" or "_udp". New service types
1115 * Additional subtypes of the primary service type (where a service
1116 * type has defined subtypes) follow the primary service type in a
1144 * When a service is registered, all the clients browsing for the registered
1146 * restricted to a smaller set of well known peers, the service can be
1149 * service type using a colon (":") as a delimeter. If subtypes are also present,
1169 * domain: If non-NULL, specifies the domain on which to advertise the service.
1180 * port: The port, in network byte order, on which the service accepts connections.
1181 * Pass 0 for a "placeholder" service (i.e. a service that will not be discovered
1201 * of the service. The client may NOT pass the NoAutoRename flag if the callback is NULL.
1202 * The client may still deregister the service at any time via DNSServiceRefDeallocate().
1232 * Add a record to a registered service. The name of the record will be the same as the
1233 * registered service's name.
1283 * - The primary txt record of a service registered via DNSServiceRegister()
1284 * - A record added to a registered service via DNSServiceAddRecord()
1293 * service's primary txt record.
1322 * Remove a record previously added to a service record set via DNSServiceAddRecord(), or deregister
1355 /* Browse for instances of a service.
1364 * interfaceIndex: The interface on which the service is advertised. This index should
1365 * be passed to DNSServiceResolve() when resolving the service.
1371 * serviceName: The discovered service name. This name should be displayed to the user,
1374 * regtype: The service type, which is usually (but not always) the same as was passed
1375 * to DNSServiceBrowse(). One case where the discovered service type may
1376 * not be the same as the requested service type is when using subtypes:
1379 * to DNSServiceBrowse(), but the type of the service that's discovered
1380 * is simply "_ftp._tcp". The regtype for each discovered service instance
1382 * DNSServiceResolve() when the service is later resolved.
1384 * domain: The domain of the discovered service instance. This may or may not be the
1386 * discovered service instance should be stored along with the name, so that
1387 * it can be passed to DNSServiceResolve() when the service is later resolved.
1420 * regtype: The service type being browsed for followed by the protocol, separated by a
1427 * will discover only the members that register the service with GroupID. See
1434 * callBack: The function to be called when an instance of the service being browsed for
1460 * Resolve a service name discovered via DNSServiceBrowse() to a target host name, port number, and
1479 * interfaceIndex: The interface on which the service was resolved.
1485 * fullname: The full service domain name, in the form <servicename>.<protocol>.<domain>.
1491 * hosttarget: The target hostname of the machine providing the service. This name can
1494 * port: The port, in network byte order, on which connections are accepted for this service.
1498 * txtRecord: The service's primary txt record, in standard txt record format.
1545 * interfaceIndex: The interface on which to resolve the service. If this resolve call is
1550 * the desired service may now be reachable via a different physical interface.
1553 * name: The name of the service instance to be resolved, as reported to the
1556 * regtype: The type of the service instance to be resolved, as reported to the
1559 * domain: The domain of the service instance to be resolved, as reported to the
1929 * to be out of date (e.g. because TCP connection to a service's target failed.)
1991 * directory service mechanism it is using to enable peers to connect to it.
1994 * and the external IP address and port for the service are recorded in the global DNS.
2173 * service: The service name - any dots or backslashes must NOT be escaped.
2177 * regtype: The service type followed by the protocol, separated by a dot
2190 const char * const service, /* may be NULL */
2578 * service: DNSServiceRef that was allocated and returned to the application, when the
2585 * Returns kDNSServiceErr_BadParam if the service param is invalid or the
2591 DNSServiceRef service,