> This happens EVERY time file is opened. The >= 2 second overhead
> probable comes for establishing the ftp connection,
Yes, I am aware of this - I didn't mention it but I probably should
have said that I feel the only realistic solution to the ftp problem
(whatever path mechanism you have) is to use dbAsciiExpand. Having
accepted this, any worry about efficiencies in path mechanisms
disappears.
Having said this, I am also leaning towards having UAE encourage users
to create an ascii equivalent of default.dctsdr (i.e. by default
expanding all.ascii) no matter whether they use nfs or ftp, and using
the expanded file wherever default.dctsdr has been used in the past.
(e.g. the expanded file would be used by medm and Capfast and loaded
separately on vxWorks). This would avoid unexpected efficiency problems
and is very similar to current working practices so would probably be
accepted easily. After all record, device and driver support get
changed far less frequently than the record definitions so why do all
those rebuilds?
Nick
- Navigate by Date:
- Prev:
Re: Ascii databases Marty Kraimer
- Next:
Single seat WRS licenses Bob Dalesio
- 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
- Navigate by Thread:
- Prev:
Re: Ascii databases Marty Kraimer
- Next:
Re: Ascii databases Marty Kraimer
- 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
|