Lines Matching refs:callBack
158 * regardless of the function or callback being used. For any given function or callback,
161 * and callback. In some cases, for a particular call, it may be that no flags are currently
174 /* MoreComing indicates to a callback that at least one more result is
192 * conjunction with "Add". An enumeration callback with the "Add"
201 * flag set, name conflicts will result in a callback. The NoAutorename flag
297 * but not necessarily more results for this particular callback function.
298 * The implication of this for client programmers is that when a callback
301 * that its UI needs to be updated. Then, later when a callback is eventually
304 * updating, not just the UI elements related to the particular callback
311 * you can no longer wait for a callback *without* MoreComing set, to tell
359 * of whether a response was given earlier or not. When the query is stopped, the callback will be called
607 * to their DNSServiceBrowseReply() callback function, and discarding those
619 * known a priori. The resolve callback will indicate the index of the
710 * reply from the socket, and pass it to the appropriate application callback. By using a run
730 * Read a reply from the daemon, calling the appropriate application callback. This call will
740 * that take a callback parameter.
798 * DNSServiceDomainEnumReply Callback Parameters:
847 * callBack: The function to be called when a domain is found or the call asynchronously
850 * context: An application context pointer which is passed to the callback function
854 * errors are delivered to the callback), otherwise returns an error code indicating
855 * the error that occurred (the callback is not invoked and the DNSServiceRef
864 DNSServiceDomainEnumReply callBack,
877 * DNSServiceRegisterReply() Callback Parameters:
881 * flags: When a name is successfully registered, the callback will be
884 * more than one success callback (e.g. one in the "local" multicast
887 * or similar problem and has to be deregistered, the callback will
888 * be invoked with the kDNSServiceFlagsAdd flag not set. The callback
939 * name is used (this name is communicated to the client via the callback).
1008 * callBack: The function to be called when the registration completes or asynchronously
1009 * fails. The client MAY pass NULL for the callback - The client will NOT be notified
1012 * of the service. The client may NOT pass the NoAutoRename flag if the callback is NULL.
1015 * context: An application context pointer which is passed to the callback function
1019 * errors are delivered to the callback), otherwise returns an error code indicating
1020 * the error that occurred (the callback is never invoked and the DNSServiceRef
1036 DNSServiceRegisterReply callBack, /* may be NULL */
1242 * callBack: The function to be called when an instance of the service being browsed for
1245 * context: An application context pointer which is passed to the callback function
1249 * errors are delivered to the callback), otherwise returns an error code indicating
1250 * the error that occurred (the callback is not invoked and the DNSServiceRef
1261 DNSServiceBrowseReply callBack,
1281 * DNSServiceResolveReply Callback Parameters:
1313 * These should be fixed by updating your own callback function definition to match the corrected
1315 * bugs in your callback function, where it could have incorrectly interpreted a length byte with value 250
1318 * this header file, you should update your callback function definition to use the correct unsigned value,
1319 * and then in the place where you pass your callback function to DNSServiceResolve(), use a cast to eliminate
1356 * callback. If this resolve call is using information previously saved
1362 * DNSServiceBrowseReply() callback.
1365 * DNSServiceBrowseReply() callback.
1368 * DNSServiceBrowseReply() callback.
1370 * callBack: The function to be called when a result is found, or if the call
1373 * context: An application context pointer which is passed to the callback function
1377 * errors are delivered to the callback), otherwise returns an error code indicating
1378 * the error that occurred (the callback is never invoked and the DNSServiceRef
1390 DNSServiceResolveReply callBack,
1405 * DNSServiceQueryRecordReply() Callback Parameters:
1439 * get another callback telling them otherwise.
1488 * callBack: The function to be called when a result is found, or if the call
1491 * context: An application context pointer which is passed to the callback function
1495 * errors are delivered to the callback), otherwise returns an error code indicating
1496 * the error that occurred (the callback is never invoked and the DNSServiceRef
1508 DNSServiceQueryRecordReply callBack,
1548 * get another callback telling them otherwise.
1598 * callBack: The function to be called when the query succeeds or fails asynchronously.
1600 * context: An application context pointer which is passed to the callback function
1604 * errors are delivered to the callback), otherwise returns an error code indicating
1615 DNSServiceGetAddrInfoReply callBack,
1652 * by the client in the callback.
1715 * callBack: The function to be called when a result is found, or if the call
1718 * context: An application context pointer which is passed to the callback function
1722 * errors are delivered to the callback), otherwise returns an error code indicating
1723 * the error that occurred (the callback is never invoked and the DNSRecordRef is
1739 DNSServiceRegisterRecordReply callBack,
1803 * The client callback will be invoked, informing the client of the NAT gateway's
1813 * It's possible that the client callback could be called multiple times, for example
1831 * the PortMapping API just invokes your callback, giving the machine's public address
1836 * - If the machine already has a routable public IP address, then your callback
1838 * - If a NAT mapping is required and obtained, then your callback will be invoked
1841 * or the machine has no network connectivity, then your callback will be
1848 * The client just needs to make one call to the PortMapping API, and its callback will
1856 * mapping and inform the client with a new callback giving the new address and port information.
1942 * callBack: The function to be called when the port mapping request succeeds or fails asynchronously.
1944 * context: An application context pointer which is passed to the callback function
1948 * errors are delivered to the callback), otherwise returns an error code indicating
1965 DNSServiceNATPortMappingReply callBack,
1984 DNSHostnameChangedReply callBack,
2235 * Receive TXT record data in DNSServiceResolve() callback
2246 * callback, then you need to copy the data to your own storage using memcpy()
2392 * If there is any error during the processing of events, the application callback will
2394 * will get its own error callback. Currently these error callbacks only happen
2414 * queue: dispatch queue where the application callback will be scheduled