On Sat, Jan 28, 2012 at 12:51 PM, Jean-Marie Gaillourdet
j...@gaillourdet.net wrote:
Hello,
On 27.01.2012, at 00:47, Alexander V Vershilov wrote:
Recently I asked about tcp server libraries [1] and there was only one
answer haskell-scallable-server [2], but in that package there was some
On 12-01-28 06:56 AM, Felipe Almeida Lessa wrote:
On Sat, Jan 28, 2012 at 9:40 AM, Yves Parèsyves.pa...@gmail.com wrote:
I think there is still no consensus on which iteratee library is the one
to use. There are at least iteratee, enumerator, iterIO, conduit, and
pipes. The reusability of your
On 28.01.2012, at 12:56, Felipe Almeida Lessa wrote:
I find it funny that conduit is said to be an iteratee library since
it has no iteratees! We've had more than one iteratee library since
at least 1.5 years with the iteratee (Mar 2009) and enumerator (Aug
2010) packages, and AFAIK now we
On Sun, Jan 29, 2012 at 10:14 AM, Jean-Marie Gaillourdet
j...@gaillourdet.net wrote:
But it does try to solve the problem, doesn't it? Obviously conduit is an
alternative to the iteratee-like packages. Why else would Yesod replace
enumerator by conduit? That is the reason why I added it into
On Sun, Jan 29, 2012 at 2:21 PM, Felipe Almeida Lessa
felipe.le...@gmail.com wrote:
On Sun, Jan 29, 2012 at 10:14 AM, Jean-Marie Gaillourdet
j...@gaillourdet.net wrote:
But it does try to solve the problem, doesn't it? Obviously conduit is an
alternative to the iteratee-like packages. Why
Hello,
On 27.01.2012, at 00:47, Alexander V Vershilov wrote:
Recently I asked about tcp server libraries [1] and there was only one
answer haskell-scallable-server [2], but in that package there was some
dependencies and server logic that are not good for my task.
A simple search for server
http://hackage.haskell.org/package/network-server
Straightforward to use, but unfortunately uses unix package. I take it it
is not portable.
However its first version did not use it, so maybe the concerned part could
be rewritten.
I think there is still no consensus on which iteratee library
Yves Parès wrote:
Yes, and IMO this is a growing problem. Since iteratees were designed, a
lot of different libraries providing this kind of service have appeared.
Thats mainly because the solution space was new and lots of unexplored
terrain.
Or else, we have to make sure that each one
On Sat, Jan 28, 2012 at 9:40 AM, Yves Parès yves.pa...@gmail.com wrote:
I think there is still no consensus on which iteratee library is the one
to use. There are at least iteratee, enumerator, iterIO, conduit, and
pipes. The reusability of your libary depends on the choice of
iteratee-style
Felipe Almeida Lessa wrote:
I find it funny that conduit is said to be an iteratee library since
it has no iteratees! We've had more than one iteratee library since
at least 1.5 years with the iteratee (Mar 2009) and enumerator (Aug
2010) packages, and AFAIK now we have four iteratee
Hello.
-- Resending reply to maillistmail
Sat, Jan 28, 2012 at 11:51:32AM +0100, Jean-Marie Gaillourdet wrote
Hello,
On 27.01.2012, at 00:47, Alexander V Vershilov wrote:
Recently I asked about tcp server libraries [1] and there was only one
answer haskell-scallable-server [2], but in
Yes, I was forecasting a little...
Concerning conduit, yes it's not another implementation of Oleg's
iteratees, yet its API looks a lot like 'enumerators'.
Plus it aims at solving the same problem, only the implementation that
differs (roughly state variables instead of pure closure-based
Hello, café.
Recently I asked about tcp server libraries [1] and there was only one
answer haskell-scallable-server [2], but in that package there was some
dependencies and server logic that are not good for my task.
So I decided to make a library with skeletons for different types of
tcp
13 matches
Mail list logo
