I also object. Not only is the X resource data base overused
(I've benchmarked applications that used 2 seconds to start up
reading the database from the server and then trying to do all
the matching), but the real problem is that the binding should
be kept with the data.
In my installation, we have one machine that everyone NFS's to
that has the face database. If the audio bindings were in the
resource file, then everyone using audio faces would also have to
place all of the binding information in their .Xdefaults file.
I liked the .au file with the face.xbm file. This follows the
current database architecture and we can then begin discussing
new database architectures. At the worst, I'd accept a bindings
file ("aubindings.tab" ?).
In ten words or less: I'd recommend that the data and the bindings
be associated with the database and the workstation/preference
specific playing programs be specified resources, parameters, ...
-- Robert Adams email@example.com