<div dir="ltr">Would you, for example, build the ranch protocol as simple as possible, and link the other application servers, as needed, with a common protocol?<div><br></div><div>-Thom</div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jan 22, 2017 at 2:56 PM Thom Cherryhomes <<a href="mailto:thom.cherryhomes@gmail.com">thom.cherryhomes@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">Hello, everyone.
This is my first post to the list.
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">I’m a long time
swiss army knife of a software and hardware engineer who has started
to pick up Erlang, because I believe it and languages like it to be
the future of software development.</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">With that said, I am
working on a personal project of mine that I have wanted to complete,
a 21<sup class="gmail_msg">st</sup> century version of a BBS system, and I believe
Erlang and OTP are a good language and toolkit to write it in.</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">Code is being
dropped here: <a href="http://github.com/tschak909/nakbbs" class="gmail_msg" target="_blank">http://github.com/tschak909/nakbbs</a></p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">I am experimenting
with both Ranch and just using gen_tcp with my own socket pools, but
I do have some design questions.</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">The telnet ports
need to present a definite series of states, broken up into seperate
pieces:</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">I have definite
common events that can be stretched across multiple use cases:</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Display</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Wait for line of
input</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Wait for character
input</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* branch to another
menu</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* hang up</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;border-top:none;border-bottom:1px solid rgb(0,0,0);border-left:none;border-right:none;padding:0in 0in 0.03in;line-height:100%" class="gmail_msg">
But there will also be definite sections of the system, which could
be thought of as states:</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Authentication</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Message Browser</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Message Editor</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">* Various Games</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">etc.</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">and I’m trying to
think of an appropriate architectural pattern that will avoid me
basically having to cram every conceivable state as a sort of
hierarchy of tuples into a single gen_statem module. How can I
approach this in a nice abstract and extensible manner, that I could
for example push into a Behaviour and subsequently utilize for
different terminal types? It would be nice to split up the different
parts of the system into applications that would essentially be
called from well defined APIs…</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">I’m just trying to
figure this all out, and would love a semblence of direction so I can
do the proper research and deeply understand what I need to learn.</p></div><div dir="ltr" class="gmail_msg">
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg">-Thom</p>
<p style="margin-bottom:0in;line-height:100%" class="gmail_msg"><br class="gmail_msg">
</p></div></blockquote></div>