EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: [Bug 1902560] Re: Read info items using a filter
From: Dirk Zimoch via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Wed, 03 Mar 2021 16:07:41 -0000
** Changed in: epics-base
     Assignee: (unassigned) => Dirk Zimoch (dirk.zimoch)

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1902560

Title:
  Read info items using a filter

Status in EPICS Base:
  Confirmed

Bug description:
  Info items are currently only accessible from inside the IOC, but a
  few people have asked if they could be fetched over the network. The
  simplest way to implement that is probably with a server-side filter,
  which makes this functionality optional and decouples the code from
  the internals of the IOC.

  The filter could accept parameters to control what it returns, such
  as:

  1. A list of all the info item names attached to this record or alias.
  2. A list of info item names attached that match a particular pattern.
  3. Number of info items attached.
  4. Value of a specific info item, selected by index number or item name.
  5. All info item names and values, formatted as a JSON object (beware that item values can now themselves be JSON objects, don't assume they are just a string).

  It would be reasonable to limit item names to 39 characters so #1 and
  #2 above could return an array of DBF_STRINGs, and #3 could return a
  DBF_SHORT or DBF_LONG, but item values can be much longer so the
  return types of #4 and #5 would need to be an array of DBF_CHAR with
  some chosen maximum length.

  CAUTION: Record aliases have their own info item namespace, separate
  from the record they alias:

  record(ai, ai1) {
    info(tag1, "record")
    alias(al1)
  }
  record("*", al1) {
    info(tag2, "alias")
  }

  epics> dbli
  ai1 info(tag1, "record")
  al1 info(tag2, "alias")

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1902560/+subscriptions

Navigate by Date:
Prev: Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Joel Sherrill via Core-talk
Next: Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Johnson, Andrew N. via Core-talk
Next: About RTEMS libbsdport networking drivers Vijay Kumar Banerjee via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 04 Mar 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·