I'm occasionally working on making a friendly yet performant library that
simultaneously builds parsers and generators, but it's non-trivial. If you
want to see the general idea, there's a Functional Pearl on pickler
combinators from a few years back that you can probably play with.
But for a real network protocol that you need to implement today, I'd go
with attoparsec or Data.Binary.
2010/10/27 Günther Schmidt gue.schm...@web.de
Hi all,
I'd like to write a client app that communicates with a server over TCP/IP.
My question is in regard which parser to use for the servers responses. I'm
quite familiar with parsec (2.x) but I'm not sure if it's the right choice
for this. The code would necessarily constantly be switching between
checking for input, interpreting and then responding.
Any suggestions?
Günther
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe