Experimental Physics and
Industrial Control System

Benjamin Franksen <[email protected]> · Wed, 20 Jul 2005 21:45:34 +0200

On Wednesday 20 July 2005 16:47, Dalesio, Leo `Bob` wrote:
> There are use cases on the wiki.
>
> There are two thoughts on this
> -- you are told the type
>
> -- you are not told the type
>
> Could we work out the use cases with either approach?

I have been thinking about this, too. I think that a better way to 
describe the two cases is

- Client knows the type, or at least knows a suitable supertype large 
enough to hold the data, eitehr by design or by user configuration. 
Examples: Display managers, command line tools (common usage), all 
applications written for a specific database.

- Client must exactly reflect the server type, but has no way of knowing 
the type beforehand. Examples are: Gateway, Archiver. I tink that only 
fully generic applications need this.

> Ben - you handle -- not told the type

This case is completely solved by Data Access. There are things in it 
that could be improved (like making streamWite and streamRead objects 
separate from string) but at least I think it contains the needed 
functionality.

> Kay - you handle -- told the type

This would be solved as soon as Jeff and Ralph manage to publish the 
PropertySurveyor interface.

Jeff: why don't you just put all the latest header files on the wiki? Or 
at least give us a link where one can download them so that we can take 
a look at the current state of affairs?

Ben

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System