Server IP : 111.118.215.189 / Your IP : 3.131.85.46 Web Server : Apache System : Linux md-in-83.webhostbox.net 4.19.286-203.ELK.el7.x86_64 #1 SMP Wed Jun 14 04:33:55 CDT 2023 x86_64 User : a1673wkz ( 2475) PHP Version : 8.2.25 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON Directory (0755) : /usr/share/emacs/24.3/lisp/net/ |
[ Home ] | [ C0mmand ] | [ Upload File ] |
---|
;ELC ;;; Compiled by mockbuild@buildfarm06-new.corp.cloudlinux.com on Fri Oct 11 10:10:39 2024 ;;; from file /builddir/build/BUILD/emacs-24.3/lisp/net/zeroconf.el ;;; in Emacs version 24.3.1 ;;; with all optimizations. ;;; This file uses dynamic docstrings, first added in Emacs 19.29. ;;; This file does not contain utf-8 non-ASCII characters, ;;; and so can be loaded in Emacs versions earlier than 23. ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (require 'dbus) #@41 Write messages during service discovery (defvar zeroconf-debug nil (#$ . 571)) #@39 The D-Bus name used to talk to Avahi. (defconst zeroconf-service-avahi "org.freedesktop.Avahi" (#$ . 656)) #@51 The D-Bus root object path used to talk to Avahi. (defconst zeroconf-path-avahi "/" (#$ . 769)) #@71 The D-Bus object path used to talk to the Avahi service type browser. (defvar zeroconf-path-avahi-service-type-browser nil (#$ . 871)) #@67 The D-Bus object paths used to talk to the Avahi service browser. (defvar zeroconf-path-avahi-service-browser-hash (make-hash-table :test 'equal) (#$ . 1012)) #@68 The D-Bus object paths used to talk to the Avahi service resolver. (defvar zeroconf-path-avahi-service-resolver-hash (make-hash-table :test 'equal) (#$ . 1177)) #@52 The D-Bus entry group interface exported by Avahi. (defconst zeroconf-interface-avahi-entry-group (concat zeroconf-service-avahi ".EntryGroup") (#$ . 1344)) #@47 The D-Bus server interface exported by Avahi. (defconst zeroconf-interface-avahi-server (concat zeroconf-service-avahi ".Server") (#$ . 1507)) #@61 The D-Bus service type browser interface exported by Avahi. (defconst zeroconf-interface-avahi-service-type-browser (concat zeroconf-service-avahi ".ServiceTypeBrowser") (#$ . 1656)) #@56 The D-Bus service browser interface exported by Avahi. (defconst zeroconf-interface-avahi-service-browser (concat zeroconf-service-avahi ".ServiceBrowser") (#$ . 1845)) #@57 The D-Bus service resolver interface exported by Avahi. (defconst zeroconf-interface-avahi-service-resolver (concat zeroconf-service-avahi ".ServiceResolver") (#$ . 2020)) #@32 Wildcard Avahi interface spec. (defconst zeroconf-avahi-interface-unspec -1 (#$ . 2198)) #@31 Wildcard Avahi protocol spec. (defconst zeroconf-avahi-protocol-unspec -1 (#$ . 2293)) #@38 Avahi INET4 address protocol family. (defconst zeroconf-avahi-protocol-inet4 0 (#$ . 2386)) #@38 Avahi INET6 address protocol family. (defconst zeroconf-avahi-protocol-inet6 1 (#$ . 2484)) #@21 Empty Avahi domain. (defconst zeroconf-avahi-domain-unspec "" (#$ . 2582)) #@40 Domain name services are resolved for. (defvar zeroconf-avahi-current-domain zeroconf-avahi-domain-unspec (#$ . 2663)) #@17 No Avahi flags. (defconst zeroconf-avahi-flags-unspec 0 (#$ . 2788)) #@1430 Hash table of discovered Avahi services. The key of an entry is the concatenation of the service name and service type of a discovered service. The value is the service itself. The format of a service is (INTERFACE PROTOCOL NAME TYPE DOMAIN FLAGS) The INTERFACE is a number, which represents the network interface the service is located at. The corresponding network interface name, like "eth0", can be retrieved with the function `zeroconf-get-interface-name'. PROTOCOL describes the used network protocol family the service can be accessed. `zeroconf-avahi-protocol-inet4' means INET4, `zeroconf-avahi-protocol-inet6' means INET6. An unspecified protocol family is coded with `zeroconf-avahi-protocol-unspec'. NAME is the string the service is known at Avahi. A service can be known under the same name for different service types. Each TYPE stands for a discovered service type of Avahi. The format is described in RFC 2782. It is of the form "_APPLICATION-PROTOCOL._TRANSPORT-PROTOCOL". TRANSPORT-PROTOCOL must be either "tcp" or "udp". APPLICATION-PROTOCOL must be a protocol name as specified in URL `http://www.dns-sd.org/ServiceTypes.html'. Typical service types are "_workstation._tcp" or "_printer._tcp". DOMAIN is the domain name the service is registered in, like "local". FLAGS, an integer, is used inside Avahi. When publishing a service (see `zeroconf-publish-service', the flag 0 is used. (defvar zeroconf-services-hash (make-hash-table :test 'equal) (#$ . 2865)) #@1120 Hash table of resolved Avahi services. The key of an entry is the concatenation of the service name and service type of a resolved service. The value is the service itself. The format of a service is (INTERFACE PROTOCOL NAME TYPE DOMAIN HOST APROTOCOL ADDRESS PORT TXT FLAGS) INTERFACE, PROTOCOL, NAME, TYPE, DOMAIN and FLAGS have the same meaning as in `zeroconf-services-hash'. HOST is the host name the service is registered. It is a fully qualified name, i.e., it contains DOMAIN. APROTOCOL stands for the network protocol family ADDRESS is encoded (`zeroconf-avahi-protocol-inet4' means INET4, `zeroconf-avahi-protocol-inet6' means INET6). It can be different from PROTOCOL, when an address resolution has been requested for another protocol family but the default one. ADDRESS is the service address, encoded according to the APROTOCOL network protocol family. PORT is the corresponding port the service can be reached on ADDRESS. TXT is an array of strings, describing additional attributes of the service. Usually, every string is a key=value pair. The supported keys depend on the service type. (defvar zeroconf-resolved-services-hash (make-hash-table :test 'equal) (#$ . 4377)) #@53 Returns all discovered Avahi service names as list. (defalias 'zeroconf-list-service-names #[nil "\302\303\304 \"\210)\207" [result zeroconf-services-hash nil maphash #[(key value) "\301\302\303!\"\207" [value add-to-list result zeroconf-service-name] 4]] 3 (#$ . 5586)]) #@53 Returns all discovered Avahi service types as list. (defalias 'zeroconf-list-service-types #[nil "\302\303\304 \"\210)\207" [result zeroconf-services-hash nil maphash #[(key value) "\301\302\303!\"\207" [value add-to-list result zeroconf-service-type] 4]] 3 (#$ . 5867)]) #@261 Returns all discovered Avahi services for a given service type TYPE. The service type is one of the returned values of `zeroconf-list-service-types'. The return value is a list (SERVICE1 SERVICE2 ...). See `zeroconf-services-hash' for the format of SERVICE. (defalias 'zeroconf-list-services #[(type) "\302\303\304 \"\210)\207" [result zeroconf-services-hash nil maphash #[(key value) "\302 !\232\205\f \303\304 \"\207" [type value zeroconf-service-type add-to-list result] 3]] 3 (#$ . 6149)]) #@86 Hash table of hooks for newly added services. The key of an entry is a service type. (defvar zeroconf-service-added-hooks-hash (make-hash-table :test 'equal) (#$ . 6654)) #@82 Hash table of hooks for removed services. The key of an entry is a service type. (defvar zeroconf-service-removed-hooks-hash (make-hash-table :test 'equal) (#$ . 6831)) #@741 Add FUNCTION to the hook of service type TYPE. EVENT must be either :new or :removed, indicating whether FUNCTION shall be called when a new service has been newly detected, or removed. FUNCTION must accept one argument SERVICE, which identifies the new service. Initially, when EVENT is :new, FUNCTION is called for all already detected services of service type TYPE. The attributes of SERVICE can be retrieved via the functions `zeroconf-service-interface' `zeroconf-service-protocol' `zeroconf-service-name' `zeroconf-service-type' `zeroconf-service-domain' `zeroconf-service-flags' `zeroconf-service-host' `zeroconf-service-aprotocol' `zeroconf-service-address' `zeroconf-service-port' `zeroconf-service-txt' (defalias 'zeroconf-service-add-hook #[(type event function) "\306\232\2036 \307 \n\310#\311\303\f\"\210\312 \n#\210\313 !\310\211\2054 @\f !\210A\211\204\"