[elephant-cvs] CVS elephant/doc

[rread]

Update of /project/elephant/cvsroot/elephant/doc
In directory clnet:/tmp/cvs-serv2667

Modified Files:
	scenarios.texinfo 
Log Message:
Added a blurb about Konsenti.


--- /project/elephant/cvsroot/elephant/doc/scenarios.texinfo	2007/03/24 13:55:15	1.1
+++ /project/elephant/cvsroot/elephant/doc/scenarios.texinfo	2007/04/02 13:09:46	1.2
@@ -23,3 +23,21 @@
 Object-oriented data storage, large graph traversals
 
 
+ at node Commercial Applications
+
+Elephant is used by Konsenti(tm), a for-profit company of Robert L. Read, one of the maintainers of Elephant.  It can be visited at
+ at uref{http://konsenti.com}.  Konsenti uses the Data Collection Management (DCM) package, which can be 
+found in the contrib directory, under user rread.  DCM provides prevalence-style in-memory write-through caching.
+The most enjoyable feature about Elephant for this project is that new Business Layer objects can be created without having to 
+deal with an Object-Relational Mapping, which has allowed extremely rapid development.  All Business objects are persisted via
+a director in DCM (which sits on top of Elephant.)  Many of these business objects are in fact finite state machines decorated 
+with functions.  The functions are represented by their lambda expression stored in slots on the business objects.  A complete
+Message Factory and double-entry accounting system are also implemented as DCM objects.  Binary objects, such as uploaded 
+PDFs that can be attached to objects as comments, are treated as simple objects and stored directly in Elephant.  Konsenti
+is completely based on utf-8, and unicode characters outside of the ISO-9959-1 character set are routinely stored in 
+Elephant.  Konsenti uses Postgres as a backend; but Elephant makes it so easy to migrate between repositories that we 
+could change this decision at any time.
+
+
+
+