g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  Index 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014 
<== Date ==> <== Thread ==>

Subject: RE: hello world examples
From: "Dalesio, Leo `Bob`" <dalesio@slac.stanford.edu>
To: "EPICS Core Talk" <core-talk@aps.anl.gov>
Date: Wed, 22 Jun 2005 05:44:11 -0700
 We are having a design meeting July 11th. 

I expect to cover the following:
Building structures and arrays - APS
Present next level of detail in the design.
Field Change Notification - APS
Next level of detail. 
Mechanism for event set - extensible? How many are needed?

Super Record - Andrew/Bob
Present a study on the ability and issues in creating super records.

User extensible fields - Marty, Kay and Matthias
Present a study on the ability to extend record funciontality with an extension of records.

Middleware Interfaces to CA server  - Ralph and Benjamin
Present the requirements and a preliminary design for a layer between the database posting mechanism and services that are interested in this data. 

Network Communication Services
Name service - Doug and Kay
Present the function and a preliminary design for the name services.

Channel Access Client user interface - Kay and Doug
Provide the user perspective of the CA Client interface.

Channel Access Client - Jeff 
Show the connection of the CA Client interface to the low level calls provided.

Channel Access Network Protocol - Jeff
Specification of the protocol on the wire will be provided prior to implementation.

Channel Access Services  - Jeff 
Show the interface from the database middle layer - and design for the filtering.

Property Catalogs and Events - Bob
Provide a list of properties and events that will be supported.

EPICS Gateway - Ralph and Benjamin
Present the requirements and preliminary design forf the gateway to support all channel access features for filtering and events.








Navigate by Date:
Prev: Re: V4 design issue: Should primitive data types have well defined precisions? Benjamin Franksen
Next: RE: V4 design issue: Should primitive data types have well defined precisions? Dalesio, Leo `Bob`
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014 
Navigate by Thread:
Prev: V4 Access Rights over DataAccess Ralph Lange
Next: RE: V4 design issue: Should primitive data types have well defined precisions? Dalesio, Leo `Bob`
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·