<p dir="ltr">Essentially I'm looking for all the things that my client needs to do in order to be called a "netrek client". I'm sure I could guess from the COW sources, but I've never done C so it would be mostly guess-and-check coding with a local server.</p>
<div class="gmail_quote">On May 13, 2015 10:44 PM, "James Cameron" <<a href="mailto:quozl@us.netrek.org">quozl@us.netrek.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Could you tell me what type of client specifications you need?<br>
<br>
We don't generally keep specifications that duplicate the sources,<br>
because then we have to maintain two artefacts; the specifications and<br>
the sources.<br>
<br>
--<br>
James Cameron<br>
<a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
_______________________________________________<br>
netrek-dev mailing list<br>
<a href="mailto:netrek-dev@us.netrek.org">netrek-dev@us.netrek.org</a><br>
<a href="http://mailman.us.netrek.org/mailman/listinfo/netrek-dev" target="_blank">http://mailman.us.netrek.org/mailman/listinfo/netrek-dev</a><br>
</blockquote></div>