Contensive Library Architecture - Revision history

Admin at 17:24, 21 December 2016

2016-12-21T17:24:20Z

Admin at 20:37, 20 December 2016

2016-12-20T20:37:49Z

Admin at 19:21, 20 December 2016

2016-12-20T19:21:03Z

Admin at 19:18, 20 December 2016

2016-12-20T19:18:32Z

Admin at 18:51, 20 December 2016

2016-12-20T18:51:25Z

Admin at 14:51, 8 November 2016

2016-11-08T14:51:33Z

Admin at 14:49, 8 November 2016

2016-11-08T14:49:52Z

Admin at 14:48, 8 November 2016

2016-11-08T14:48:31Z

Admin: Admin moved page Contensive SMS Architectural Overview to Contensive Library Architecture: Clarify

2016-11-05T22:54:07Z

Admin moved page Contensive SMS Architectural Overview to Contensive Library Architecture: Clarify

Admin at 21:18, 12 December 2015

2015-12-12T21:18:28Z

← Older revision		Revision as of 17:24, 21 December 2016
Line 10:		Line 10:
	For developers, the following diagram outlines the underlying system architecture		For developers, the following diagram outlines the underlying system architecture

−	[[File:~~ContensiveBlockDiagram~~.png]]	+	[[File:ContensiveBlockDiagrams.png]]

@@ Line 3: / Line 3: @@
 * Separate design from code - so designers and UI/UX professionals can use native tools to create and modify.
-* Isolate and abstract hardware services - To facilitate mocking for integration testing, to minimize infrastructure lock-in, to .
+* Isolate and abstract hardware services - To facilitate mocking for unit/integration testing, to minimize infrastructure lock-in.
 * To prevent lock-in to this library by focusing on replaceable modularity - low coupling and high coherence.
 * To encourage rapid development by isolating business logic layer

@@ Line 5: / Line 5: @@
 * Isolate and abstract hardware services - To facilitate mocking for integration testing, to minimize infrastructure lock-in, to .
 * To prevent lock-in to this library by focusing on replaceable modularity - low coupling and high coherence.
 * Facilitate content administration.
@@ Line 10: / Line 11: @@
 [[File:ContensiveBlockDiagram.png]]

@@ Line 1: / Line 1: @@
-The Contensive Library (clib) provides methods to assist with internet applications and websites with the following goals: <br />
+The Library has the following goals: <br />
-* Separate design from code so designers and UI/UX professionals can use native tools to create and modify.
+* Separate design from code - so designers and UI/UX professionals can use native tools to create and modify.
-* Provide easy ways for server-side developers to manipulate design elements.
+* Isolate and abstract hardware services - To facilitate mocking for integration testing, to minimize infrastructure lock-in, to .
-* Move the site control and management from IT to the content administrator.
+* To prevent lock-in to this library by focusing on replaceable modularity - low coupling and high coherence.
-* Focus on application lifecycle support.
+* Facilitate content administration.
 For developers, the following diagram outlines the underlying system architecture

@@ Line 1: / Line 1: @@
 The Contensive Library (clib) provides methods to assist with internet applications and websites with the following goals: <br />
@@ Line 5: / Line 6: @@
 * Move the site control and management from IT to the content administrator.
 * Focus on application lifecycle support.
 There are several aspects of a typical application: <br />

@@ Line 8: / Line 8: @@
 There are several aspects of a typical application: <br />
 #The application root (application hosting environment like aspx or java). The hosting page contains a short script, written in a script language like php or aspx. On each request (page hit) the hosting page creates an instance of the rendering client, sets the client's request context, calls the client's getDoc() method, and processes the results. This part of the application gives the developer flexibility to quickly addresses issues in the scripting environment. Generally there is only one hosting page needed for the site(s).
-#The Rendering Client. The rendering client is an object created by the hosting language that converts requests from user clients (often browsers) into fully rendered responses (pages). All application traffic goes through the Rendering Client.
+#The Rendering Client. For contensive this is cp.The rendering client is an object created by the hosting language that converts requests from user clients (often browsers) into fully rendered responses (pages). All application traffic goes through the Rendering Client.
-#The Server. The server acts as a persistent store and a task scheduling.
+#The Server. The server provides a local persistent store and a task scheduler.
 #The Background Processing Environment. Application tasks that can be run offline can be transferred to background processes. For example, the ecommerce addon includes background processing for periodic charges, invoicing, etc.
 Pages are rendered using several primary components: <br />

← Older revision		Revision as of 14:48, 8 November 2016
Line 1:		Line 1:
−	The Contensive ~~Framework~~ (~~cfw~~) ~~creates an~~ internet ~~application framework~~ with the following goals: <br />	+	The Contensive Library (clib) provides methods to assist with internet applications and websites with the following goals: <br />

	* Separate design from code so designers and UI/UX professionals can use native tools to create and modify.		* Separate design from code so designers and UI/UX professionals can use native tools to create and modify.

← Older revision	Revision as of 22:54, 5 November 2016
(No difference)