stable library
interface. I don't know anyone now who *ever* writes X
protocol code, and I've never met anyone (except a few people I once
knew who worked on a commercial X server, and even that was more than
15 years ago).
This is irrelevant. Xrm has nothing to do with the X protocal, and you can
fons - i wasn't talking about xrm at all. i was referring to the way
that X encapulsates the X protocol in Xlib, and nobody ever deals with
the protocol itself. The protocol is the true definition of X, but
nobody uses it, and with good reason.
Its also been
a *very* useful approach as JACK has evolved. We have
modified the protocol several times without requiring client
recompilation.
This is an API, not a file format.
There is a protocol involved in server/client communication. Its
isomorphous to a file format.