Martin,
This is the same issue with OpenSSL. If you have it, use it; otherwise,
use whatever else is available. The application programs that might use
the driver have the same issues. You could do it also with mode codes,
but that is counterproductive in view of the shrill rhetoric to use
POSIX if available.
Dave
Martin Burnicki wrote:
Dave,
David L. Mills wrote:
Bruce & Co.,
You may not be aware that all Spectracom devices are supported with one
driver, all TrueTime devices are supported with one driver, all
telephone modem services are supported with one driver, all Austron
devices are supported with one driver, all Heath devices are supported
with one driver and most GPS receivers are supported with one driver.
This happened with many hours of dedicated effort on the part of
refclock developers. You can appreciate the serious pushback in creating
a new driver if a similar one is already available. An appropriate plan is
[common interface code]
#ifdef POSIX
...
#else
...
#endif
How do you know which application is feeding the SHM driver, and whether
that application supports the Posix or the non-Posix (legacy) SHM mode?
IMO the legacy SHM mode should always be compiled in, and the POSIX mode in
addition, if that Posix SHM is supported by the target OS.
Whether addressing of either mode is done by separate driver numbers (which
I still find a good idea in this case, since SHM is a generic driver), or
by a mode number for the existing SHM driver, is a totally different
question.
Martin
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
