File: browserapi.xml

package info (click to toggle)
libdmapsharing 3.9.13-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 3,340 kB
  • sloc: ansic: 17,285; sh: 4,782; xml: 556; makefile: 459
file content (37 lines) | stat: -rw-r--r-- 1,225 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
<?xml version="1.0"?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
               "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
]>
<refentry id="browserapi">
	<refmeta>
		<refentrytitle>mDNS Browser API</refentrytitle>
		<manvolnum>3</manvolnum>
		<refmiscinfo>Libdmapsharing</refmiscinfo>
	</refmeta>

	<refnamediv>
		<refname>mDNS Browser API</refname>
		<refpurpose>
			Using the mDNS browser API
		</refpurpose>
	</refnamediv>

	<refsect1>
		<title>mDNS Browser API</title>
		<para>
The mDNS browser API allows a client program to discover and connect to
DMAP services.  The dmap_mdns_browser_new function creates a new mDNS
browser object. Passing DMAP_MDNS_SERVICE_TYPE_DAAP to this function
results in a DAAP browser, and passing DMAP_MDNS_SERVICE_TYPE_DPAP results in
a DPAP browser. Subsequently calling dmap_mdns_browser_start and g_main_loop_run
causes the browser to begin watching for services of the appropriate type.

		</para>
		<para>
The mDNS browser object emits a "service-added" signal for each
DMAP service encountered, and it emits a "service-remove" signal when
a service disappears. We describe these callbacks in the next sections.

		</para>
	</refsect1>
</refentry>