Customer Application Framework - Revision history

Cbilodeau: fix link

2012-05-08T20:13:01Z

fix link

Jasmin Letendre: Added link to page 'Working with Call Legs'

2011-01-18T13:56:19Z

Added link to page 'Working with Call Legs'

Ktrueman: added category

2009-11-17T14:33:14Z

added category

Ktrueman: added link to CAF category and associated articles

2009-10-22T16:06:59Z

added link to CAF category and associated articles

Ktrueman: initial content; copied from toolpack guide

2009-07-24T15:36:14Z

initial content; copied from toolpack guide

New page

The Customer Application Framework (CAF) library comes in where the [[CMC library]] left off. The main purpose is to provide a set of optional C++ classes that may be used to easily implement gateway applications. The CAF classes build on CMC legs and provide easier management of calls, [[CLI]], memory, logger, database, etc. CMC samples and applications are built on this framework since the code is easier to understand and the development time is shortened.

==The optional nature of CAF ==
Clients should not need to integrate in a really big framework just to use one of the framework's helper classes. This is why each individual element of the framework is designed to be optional and independent. For example it is not mandatory to use a routing class to create a call class.

== The customization of CAF ==
Of course the framework will not address all of the clients needs perfectly. This is why most of the classes may be subclassed or re-implemented to provide a better fit and still be used in the rest of the framework. For example the data access object for a client account may be reimplemented to query a non supported database. This DAO could then be used in the gateway application with minor modifications.

@@ Line 12: / Line 12: @@
 ==References==
-*[http://docs.telcobridges.com/mediawiki/index.php/Category:CAF Articles concerning CAF]
+*[[:Category:CAF|Articles concerning CAF]]
-[[category:CAF]]
+[[Category:CAF]]

← Older revision		Revision as of 13:56, 18 January 2011
Line 9:		Line 9:
	Of course the framework will not address all of the clients needs perfectly. This is why most of the classes may be subclassed or re-implemented to provide a better fit and still be used in the rest of the framework. For example the data access object for a client account may be reimplemented to query a non supported database. This DAO could then be used in the gateway application with minor modifications.		Of course the framework will not address all of the clients needs perfectly. This is why most of the classes may be subclassed or re-implemented to provide a better fit and still be used in the rest of the framework. For example the data access object for a client account may be reimplemented to query a non supported database. This DAO could then be used in the gateway application with minor modifications.

		+	Refer to [[CAF:_Working_With_Call_Legs\|Working_With_Call_Legs]] for details on how to work with call legs.

	==References==		==References==

← Older revision		Revision as of 14:33, 17 November 2009
Line 11:		Line 11:

	==References==		==References==
−	*[http://docs.telcobridges.com/mediawiki/index.php/Category:CAF Articles concerning CAF].	+	*[http://docs.telcobridges.com/mediawiki/index.php/Category:CAF Articles concerning CAF]
		+
		+
		+
		+	[[category:CAF]]

← Older revision		Revision as of 16:06, 22 October 2009
Line 8:		Line 8:
	== The customization of CAF ==		== The customization of CAF ==
	Of course the framework will not address all of the clients needs perfectly. This is why most of the classes may be subclassed or re-implemented to provide a better fit and still be used in the rest of the framework. For example the data access object for a client account may be reimplemented to query a non supported database. This DAO could then be used in the gateway application with minor modifications.		Of course the framework will not address all of the clients needs perfectly. This is why most of the classes may be subclassed or re-implemented to provide a better fit and still be used in the rest of the framework. For example the data access object for a client account may be reimplemented to query a non supported database. This DAO could then be used in the gateway application with minor modifications.
		+
		+
		+	==References==
		+	*[http://docs.telcobridges.com/mediawiki/index.php/Category:CAF Articles concerning CAF].