jan Wed, 04 Sep 2013 14:43:30 +0000
Modified page: http://wiki.horde.org/CustomizeApis
New Revision: 7
Change log: Fix link
@@ -1,7 +1,7 @@
+ Replacing APIs with your own solutions
-Horde applications are loosely coupled with each other through the
application APIs. Each application provides a set of external API
methods that can be called from other Horde applications through the
Horde Registry, or even externally through the Horde RPC interfaces.
See the ((Doc/Dev/RegistryH3|Registry wiki page)) for details.
+Horde applications are loosely coupled with each other through the
application APIs. Each application provides a set of external API
methods that can be called from other Horde applications through the
Horde Registry, or even externally through the Horde RPC interfaces.
See the ((Doc/Dev/Registry|Registry wiki page)) for details.
If you want to provide some functionality through your own or some
external code, all you need to do it to register you own code in the
Horde Registry and provide the required API methods. For example, if
you have your own address book or CRM solution, you could replace
Horde's address book module Turba with that program.
Here is a real world example. Say we have a CRM system that is
providing contacts. First create a small application stub, a Horde
mini-application. We call it "crm" and need the following 3 files to
become a working Horde module:
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
