I&#39;m occasionally working on making a friendly yet performant library that simultaneously builds parsers and generators, but it&#39;s non-trivial. If you want to see the general idea, there&#39;s a Functional Pearl on pickler combinators from a few years back that you can probably play with.<div>
<br></div><div>But for a real network protocol that you need to implement today, I&#39;d go with attoparsec or Data.Binary.<br><br><div class="gmail_quote">2010/10/27 Günther Schmidt <span dir="ltr">&lt;<a href="mailto:gue.schmidt@web.de">gue.schmidt@web.de</a>&gt;</span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
I&#39;d like to write a client app that communicates with a server over TCP/IP.<br>
<br>
My question is in regard which parser to use for the servers responses. I&#39;m quite familiar with parsec (2.x) but I&#39;m not sure if it&#39;s the right choice for this. The code would necessarily constantly be switching between checking for input, interpreting and then responding.<br>

<br>
Any suggestions?<br>
<br>
Günther<br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</blockquote></div><br></div>