\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\part{ eGroupWare/phpGroupWare Compatibility Layer}
\textsl{(Note: the tarball got lost.)}

The attached tarball can be used as a stub Horde application with HEAD versions of Horde (3.2 and later) to map xml-rpc calls that expect phpgw's API into Horde.

\section{ Setup}
First add the following code to horde/config/registry.php:

\begin{verbatim}

$this->applications['phpgw'] = array(
    'fileroot' => dirname(__FILE__) . '/../phpgw',
    'webroot' => $this->applications['horde']['webroot'] . '/phpgw',
    'name' => _("phpGW Adaptor"),
    'status' => 'notoolbar',
    'provides' => 'phpgw',
);
\end{verbatim}

Then extract the attached package into the horde directory.

Now you may read your calendar with any eGroupWare/phpGroupWare compatible calendar application.\newline
Use \texttt{http[s]://<host>/path/to/horde/rpc.php?phpgw} as server side url.

\section{ How it works}
Each xmlrpc request using a phpgw unique name is implemented by this module mapping it into horde registry commands.\newline
A lot of data is stored in the horde datatree, to map kronolith calendar ids into numeric phpgw one's.

\end{document}
