<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1474562379647_161536"><span>Josh,</span></div><div id="yui_3_16_0_ym19_1_1474562379647_161472"><span><br></span></div><div id="yui_3_16_0_ym19_1_1474562379647_161481"><span id="yui_3_16_0_ym19_1_1474562379647_161479">Have you looked at Scribble? <a href="http://scribble.org/" class="" id="yui_3_16_0_ym19_1_1474562379647_161478">http://scribble.org/</a></span></div><div id="yui_3_16_0_ym19_1_1474562379647_161537"><br></div><div id="yui_3_16_0_ym19_1_1474562379647_161587"><br></div><div id="yui_3_16_0_ym19_1_1474562379647_161586"><br></div><div id="yui_3_16_0_ym19_1_1474562379647_161471"><br></div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 13px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font size="2" face="Arial"> On Wednesday, September 21, 2016 10:45 PM, Josh Adams <josh.rubyist@gmail.com> wrote:<br></font></div> <br><br> <div class="y_msg_container"><div id="yiv9257950190"><div dir="ltr">So I've been frustrated lately by the fact that Slack's IRC gateway isn't RFC 2812 compliant (<a rel="nofollow" target="_blank" href="https://github.com/bitwalker/exirc/issues/51">https://github.com/bitwalker/exirc/issues/51</a>)<div><br></div><div>In dealing with this I wondered why the crap they needed an engineer to go through the spec as a result of their server's response to figure out that this was an issue (they've added it to their bug tracker, so I have some amount of faith it might get fixed eventually - for now I'll paper over the issue in the client which reduces the stress on them to actually fix it though).</div><div><br></div><div>Should RFCs / protocols of this nature just come with something like a quickcheck model for their spec? Is anyone aware of prior art around this sort of thing aside from Quvic/Volvo that I could draw from if I wanted to fiddle in this arena?</div><div><br></div><div>I'd think that the ideal situation involves an open source quickcheck implementation to test a given protocol implementation against at least some of the RFC, and a means to run the tests against potential servers/clients, with badges potentially showing the percentage of the test that passes. This would allow economics to drive spec implementers towards correctness, which would save countless engineer-hours spent figuring out why the damn clients can't talk to the damn servers for a given spec.</div><div><br></div><div>Thoughts? Pipe dream? "Silly child, see A, B, and C for the many people who are already doing this?"<br clear="all"><div><br></div>-- <br><div class="yiv9257950190gmail_signature">Josh Adams<br></div>
</div><img src="http://t.sidekickopen65.com/e1t/o/5/f18dQhb0S7ks8dDMPbW2n0x6l2B9gXrN7sKj6v4dY_WW8r56Rz643_PgW2B8dD01pctGFW5PXYkH1k1H6H0?si=4827575526621184&pi=db5006c4-7640-4826-df8e-17e939e11c75" style="display:none!important;" height="1" width="1"></div></div><br>_______________________________________________<br>erlang-questions mailing list<br><a ymailto="mailto:erlang-questions@erlang.org" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br><a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br><br><br></div> </div> </div> </div></div></body></html>