<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Introduction</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="GIO Reference Manual">
<link rel="up" href="pt01.html" title="Part I. GIO Overview">
<link rel="prev" href="pt01.html" title="Part I. GIO Overview">
<link rel="next" href="ch02.html" title="Compiling GIO applications">
-<meta name="generator" content="GTK-Doc V1.13 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.18 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
-<link rel="part" href="pt01.html" title="Part I. GIO Overview">
-<link rel="chapter" href="ch01.html" title="Introduction">
-<link rel="chapter" href="ch02.html" title="Compiling GIO applications">
-<link rel="chapter" href="ch03.html" title="Running GIO applications">
-<link rel="chapter" href="extending-gio.html" title="Extending GIO">
-<link rel="part" href="pt02.html" title="Part II. API Reference">
-<link rel="chapter" href="file_ops.html" title="File Operations">
-<link rel="chapter" href="file_mon.html" title="File System Monitoring">
-<link rel="chapter" href="async.html" title="Asynchronous I/O">
-<link rel="chapter" href="conversion.html" title="Data conversion">
-<link rel="chapter" href="streaming.html" title="Streaming I/O">
-<link rel="chapter" href="types.html" title="File types and applications">
-<link rel="chapter" href="volume_mon.html" title="Volumes and Drives">
-<link rel="chapter" href="icons.html" title="Icons">
-<link rel="chapter" href="failable_initialization.html" title="Failable Initialization">
-<link rel="chapter" href="networking.html" title="Lowlevel platform-independent network support">
-<link rel="chapter" href="resolver.html" title="DNS resolution">
-<link rel="chapter" href="highlevel-socket.html" title="Highlevel network functionallity">
-<link rel="chapter" href="utils.html" title="Utilities">
-<link rel="chapter" href="extending.html" title="Extending GIO">
-<link rel="part" href="migrating.html" title="Part III. Migrating to GIO">
-<link rel="chapter" href="ch19.html" title="Migrating from POSIX to GIO">
-<link rel="chapter" href="ch20.html" title="Migrating from GnomeVFS to GIO">
-<link rel="chapter" href="gio-hierarchy.html" title="Object Hierarchy">
-<link rel="index" href="api-index-full.html" title="Index">
-<link rel="index" href="api-index-deprecated.html" title="Index of deprecated symbols">
-<link rel="index" href="api-index-2-18.html" title="Index of new symbols in 2.18">
-<link rel="index" href="api-index-2-20.html" title="Index of new symbols in 2.20">
-<link rel="index" href="api-index-2-22.html" title="Index of new symbols in 2.22">
-<link rel="index" href="api-index-2-24.html" title="Index of new symbols in 2.24">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
<th width="100%" align="center">GIO Reference Manual</th>
<td><a accesskey="n" href="ch02.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
</tr></table>
-<div class="chapter" title="Introduction">
+<div class="chapter">
<div class="titlepage"><div><div><h2 class="title">
-<a name="id527914"></a>Introduction</h2></div></div></div>
+<a name="id493883"></a>Introduction</h2></div></div></div>
<p>
GIO is striving to provide a modern, easy-to-use VFS API that sits
at the right level in the library stack. The goal is to overcome the
shortcomings of GnomeVFS and provide an API that is so good that
developers prefer it over raw POSIX calls. Among other things
- that means using GObject. It also means not cloning the POSIX
+ that means using GObject. It also means not cloning the POSIX
API, but providing higher-level, document-centric interfaces.
</p>
<p>
</tbody>
</table></div>
<p>
- There is support for network programming, including name resolution, lowlevel socket
- APIs and highlevel client and server helper classes:
+ There is a framework for storing and retrieving application settings:
+ </p>
+<div class="variablelist"><table border="0">
+<col align="left" valign="top">
+<tbody><tr>
+<td><p><span class="term">GSettings</span></p></td>
+<td><p>stores and retrieves application settings</p></td>
+</tr></tbody>
+</table></div>
+<p>
+ There is support for network programming, including connectivity monitoring,
+ name resolution, lowlevel socket APIs and highlevel client and server
+ helper classes:
</p>
<div class="variablelist"><table border="0">
<col align="left" valign="top">
<td><p><span class="term">GSocketConnection</span></p></td>
<td><p>network connection stream</p></td>
</tr>
+<tr>
+<td><p><span class="term">GNetworkMonitor</span></p></td>
+<td><p>network connectivity monitoring</p></td>
+</tr>
+</tbody>
+</table></div>
+<p>
+ There is support for connecting to D-Bus,
+ sending and receiving messages, owning and watching bus names,
+ and making objects available on the bus:
+ </p>
+<div class="variablelist"><table border="0">
+<col align="left" valign="top">
+<tbody>
+<tr>
+<td><p><span class="term">GDBusConnection</span></p></td>
+<td><p>a D-Bus connection</p></td>
+</tr>
+<tr>
+<td><p><span class="term">GDBusMethodInvocation</span></p></td>
+<td><p>for handling remove calls</p></td>
+</tr>
+<tr>
+<td><p><span class="term">GDBusServer</span></p></td>
+<td><p>helper for accepting connections</p></td>
+</tr>
+<tr>
+<td><p><span class="term">GDBusProxy</span></p></td>
+<td><p>proxy to access D-Bus interfaces on a remote object</p></td>
+</tr>
</tbody>
</table></div>
<p>
Beyond these, GIO provides facilities for file monitoring,
- asynchronous I/O and filename completion. In addition to the
- interfaces, GIO provides implementations for the local case.
- Implementations for various network file systems are provided
+ asynchronous I/O and filename completion. In addition to the
+ interfaces, GIO provides implementations for the local case.
+ Implementations for various network file systems are provided
by the GVFS package as loadable modules.
</p>
<p>
Other design choices which consciously break with the GnomeVFS
design are to move backends out-of-process, which minimizes the
dependency bloat and makes the whole system more robust. The backends
- are not included in GIO, but in the separate GVFS package. The GVFS
- package also contains the GVFS daemon, which spawn further mount
+ are not included in GIO, but in the separate GVFS package. The GVFS
+ package also contains the GVFS daemon, which spawn further mount
daemons for each individual connection.
</p>
<div class="figure">
<div class="figure-contents"><div><img src="gvfs-overview.png" alt="GIO in the GTK+ library stack"></div></div>
</div>
<br class="figure-break"><p>
- The GIO model of I/O is stateful: if an application establishes e.g.
- a SFTP connection to a server, it becomes available to all applications
- in the session; the user does not have to enter his password over
+ The GIO model of I/O is stateful: if an application establishes e.g.
+ a SFTP connection to a server, it becomes available to all applications
+ in the session; the user does not have to enter his password over
and over again.
</p>
<p>
- One of the big advantages of putting the VFS in the GLib layer
+ One of the big advantages of putting the VFS in the GLib layer
is that GTK+ can directly use it, e.g. in the filechooser.
</p>
</div>
<div class="footer">
<hr>
- Generated by GTK-Doc V1.13</div>
+ Generated by GTK-Doc V1.18</div>
</body>
</html>
\ No newline at end of file
projects / platform / upstream / glib2.0.git / blobdiff