Re: example channelRPC for services

[White, G. <gr...@sl...>]

Going back to an old email just to add +1. So, we'll call "Primitive" types the types native to pvData. Not convinced about the specific name "Service type" but it'll do for now to make the distinction. Formalizing these is deliverable 7 [1]

Cheers
Greg

[1] http://epics-pvdata.sourceforge.net/charter.html#deliverables


On 15 Aug 2011, at 21:26, Marty Kraimer wrote:

> Just a couple of comments.
> 
> About Documentation.
> 
> I think we have a problem with the word "type".
> 
> pvData defines what it means by type, i.e. scalar, array, structure, and 
> structureArray and in addition scalarType.
> 
> But then what is timeStamp, alarm, table, image, etc. It is nice to also 
> call these types.
> 
> So what to do?
> 
> How about the following definitions for service types
> 
> The primitive types are the pvData scalar and array types.
> A service type is a well defined pvData structure or structureArray type.
> For example alarm, timeStamp, table, image, etc are all service types.
> 
> A correction.
> 
> In a previous message I said that if a channelGet request is attached to 
> the entire record then the data for the entire is record is returned 
> each time a get request is issued.
> 
> This is not true. The entire data is returned for the first get. 
> Additional gets only transfer data for fields that have changed since 
> the last get request.
> 
> Marty
> 
> ------------------------------------------------------------------------------
> uberSVN's rich system and user administration capabilities and model 
> configuration take the hassle out of deploying and managing Subversion and 
> the tools developers use with it. Learn more about uberSVN and get a free 
> download at:  http://p.sf.net/sfu/wandisco-dev2dev