1994 1995 1996 1997 1998 1999 2000 2001 2002 <2003> 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 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: Among the things for which I wish... |
From: | Noboru Yamamoto <[email protected]> |
To: | Jeff Hill <[email protected]> |
Cc: | "'Pete R Jemian'" <[email protected]>, "'EPICS-tech-talk'" <[email protected]> |
Date: | Tue, 18 Nov 2003 10:25:51 +0900 |
"wild carding" is usefull functionalily but we don't need to restrict ourselves to it.
Just two comments.
1) Why we need to restrict ourselfe to LDAP? I agree that LDAP is a good choice at the moment, but we don't know 5 years later. And EPICS core life will be much longer than that. At least, we have to have a layer to separate LDAP dependent part from other.
2) This functionality should be optional. User of EPICS should be able to start a simple thing in a simple way.
How this is integrated is certainly a big issue. For instance, I'm not fond of requiring that an EPICS site must build and install LDAP prior to installing or using EPICS base. However, a competing thought is that it would be nice to come up with a fairly consistent solution between sites providing wildcard based name resolution. I do agree that placing all of our eggs in the LDAP basket might be risky. Needs more thought.
The CA gateway has built-in caching directory service capabilities which are
already being used as a mechanism for scaling EPICS systems. However, this
does not provide wild carding capabilities. Since they are open source, and
already implemented, then the wildcard features in systems such as LDAP are
certainly attractive.
Jeff
-----Original Message----- From: Noboru Yamamoto [mailto:[email protected]] Sent: Monday, November 17, 2003 4:42 PM To: Jeff Hill Cc: 'Pete R Jemian'; EPICS-tech-talk Subject: Re: Among the things for which I wish...
Jeff Hill wrote:
<snip>list to
We are considering making changes so that an IOC uploads its record
an LDAP server when its databases are loaded. Among other benefits thislibraries.
would allow for wildcard queries using open source LDAP client
One of my papers at ICALEPCS 03 discusses some of the issuessurrounding the
use of EPICS in WAN.Just two comments.
Jeff
1) Why we need to restrict ourselfe to LDAP? I agree that LDAP is a good choice at the moment, but we don't know 5 years later. And EPICS core life will be much longer than that. At least, we have to have a layer to separate LDAP dependent part from other.
2) This functionality should be optional. User of EPICS should be able to start a simple thing in a simple way.
Noboru