<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - protocol: XML files need to be installed and discoverable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=55183#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - protocol: XML files need to be installed and discoverable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=55183">bug 55183</a>
from <span class="vcard"><a class="email" href="mailto:bostik.fdo@bostik.iki.fi" title="Mika Boström <bostik.fdo@bostik.iki.fi>"> <span class="fn">Mika Boström</span></a>
</span></b>
<pre>Just adding my 0.02€ as discussed on IRC.
When we developed a custom extension for a client, our *own* developers
requested that I include all the XML files in our packages, both stock and the
ones we had written, for general convenience.
Sure - the raw protocol descriptions are technically useless for C/C++ code
where the bindings are known at build time, and code is always built against
generated headers. But I can see the case for something higher-level where the
core protocol is implemented statically and the server extensions are
discovered at runtime.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>