EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Video Conference tomorrow
From: Ralph Lange <[email protected]>
To: EPICS Core Talk <[email protected]>
Date: Mon, 12 Sep 2005 10:52:19 +0200
Hmmm ....
What does the user see?                                            Either Kay or Jeff or Ralph
I think this is actually two topics (and I don't remember my name being associated with either one):

  V4 User Interface to Channel Access
  V4 User Interface to Data

While there are heavy cross dependencies between those two, they are really separate in terms of what things are interfacing to.

I'd actually be more interested in getting an agreement on the general structure of the client side:
  • Should base contain simplified versions of both CA and DA interfaces? (Which some might call "user-friendly", others wouldn't...)
  • Or only a simplified Data Interface?
    If yes: Which Data Interface should the CA User Interface use, then?
    Only the simplified, which takes away the possibility to create a client that uses DA directly?
    Only DA, which makes it hard to use a simplified Data Interface with CA?
If we agree on which interfaces go where and which library layers are there to satisfy different personal interface taste, it would be a lot easier to put name tags on all those things.
How do you call data access to get that to work?      Jeff or Ralph
This really is the problem of whoever implements a library layer that adopts other interfaces to the low-level stuff.
And noone will be able to come up with a reasonable answer before you define "that".


One other issue: I do think that we should try soon (and hard) to define and find general EPICS-wide interfaces for the complex types (strings, structs, arrays, maps, hashes, ...) - still not having decided how to handle these is really keeping other interface definitions from getting closer to final.

See you tomorrow!
Ralph

ps. I still can't find your notes of the last meeting on the wiki. Didn't we agree on your and my version being accessible to have something less biased than everyone's own memories?


Bob Dalesio wrote:
I still do not see how what the user sees and how that connects to the Data Access layer.
Am I just missing it? It would not be the first time.

So really - two things -
What does the user see?                                            Either Kay or Jeff or Ralph
How do you call data access to get that to work?      Jeff or Ralph

Bob


Navigate by Date:
Prev: RE: Video Conferencing Dayle Kotturi
Next: [Fwd: Moving event generator and event receiver record support out of base] Andrew Johnson
Index: 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Data Descriptor Interface - enum or functional or both? Ralph Lange
Next: [Fwd: Moving event generator and event receiver record support out of base] Andrew Johnson
Index: 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·