Files
epics-base/src/cas
2002-06-25 22:25:58 +00:00
..
2002-05-29 00:19:31 +00:00
2002-06-25 22:25:58 +00:00
2002-05-29 17:40:43 +00:00
2001-03-08 22:05:58 +00:00
2000-10-13 01:20:39 +00:00
1996-06-20 00:28:19 +00:00
1996-06-20 00:28:19 +00:00
doc
1996-11-22 19:41:05 +00:00
1999-09-02 21:50:29 +00:00

$Id$

README file for the EPICS Channel Access Server

Author Jeff Hill johill@lanl.gov 

$Log$
Revision 1.1.1.1  1996/06/20 00:28:06  jhill
ca server installation


Directory Structure
-------------------
o example - 		example server tool
o generic - 		generic server lib source code 
o os -			os dependnet server lib source code
o io -			io dependnet server lib source code
o build/singleThread -	server lib object code for single threaded use 
o build/multiThread -	server lib object code for multi threaded use 

Internal Source Code Naming Conventions
---------------------------------------
o API class X will almost always have associated internal (usually 
	private base) class named XI
o for class X there will 
	o sometimes be X.h - the class declaration (and simple inlines)
	o sometimes be XIL.h - complex inline functions (that will not
		compile unless the compiler has seen
		the declarations of other classes)
	o be X.cc - all other source code for the class