EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  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  <19961997  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: EPICS Access Security
From: Andy Foster <[email protected]>
To: Deb Kerstiens <[email protected]>
Cc: [email protected]
Date: Thu, 22 Feb 1996 10:10:16 +0000 (GMT)
Deb,

Thanks for your answer regarding the interaction of access security and
"dm". The Gemini Project certainly has a vested interest in what is
going to be implemented. Broadly speaking your suggestions for each 
scenario seemed fine, i.e.


FIELD_ACCESS	MONITOR	"dm" ACTION	CONTROLLER "dm" ACTION

Read_Only	No change from now.	Value displayed but I think
		Just display value.     there should always be some
					indication that this
					channel cannot be written to
					because of security. By always
					I mean not just when someone
					tries to write to it.

Read & Write	No change from now.	No change from now.

Write_Only	I don't imagine ever using this combination.

No Read		Box of a certain	Box of the same colour
or Write	colour appears saying:	appears saying:
		"Read Access Denied"    "Write Access Denied"


As far as colour (or color) rules are concerned, I haven't used these
very much, but one thought I had was assigning one colour specifically
for access problems. That way, it would be immediately obvious to the
user that the problem was one of access security. 

With dynamic graphics, I agree with Deb and believe it is not a good 
idea to just not have the graphic show up. 
I think there should always be something 
which explicitly says "Read Access Denied" or "Write Access Denied". 

Obviously, I realise that at the moment, you are trying to gather together
the "user requirements". But do you have a feel for how long it would
take to make these sort of changes to the code? 

Cheers,

Andy

===================================================================================
Andy Foster
Royal Greenwich Observatory	Tel:       44 (0)1223 374899 (direct)
Madingley Road			Fax:       44 (0)1223 374700
Cambridge			E-mail:    [email protected]
CB3 0HA				Home Page: http://www.ast.cam.ac.uk/~ajf
UK


Replies:
Re: EPICS Access Security watson
References:
Re: EPICS Access Security Deb Kerstiens

Navigate by Date:
Prev: Re: EPICS Access Security Philip Taylor
Next: Re: EPICS Access Security watson
Index: 1994  1995  <19961997  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 
Navigate by Thread:
Prev: Re: EPICS Access Security Philip Taylor
Next: Re: EPICS Access Security watson
Index: 1994  1995  <19961997  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·