Hi!
Thanks to all who responded! I got a lot of information to read and think about.
For now I decided to use stm-channelize as the simplest approach which
seem to be enough.
On Mon, Mar 5, 2012 at 9:50 PM, Alexander V Vershilov
wrote:
> Hello.
>
> I've also written simple chat server based on c
Hello.
I've also written simple chat server based on conduits and stm channels
https://github.com/qnikst/chat-server/blob/master/src/Main.hs
it has quite similar aproach and maybe this solution can be used together
to have better results.
--
Alexander Vershilov
Sat, Mar 03, 2012 at 02:05:17AM
On Sat, Mar 3, 2012 at 12:50 PM, Alp Mestanogullari wrote:
> That's exactly what I would have needed, several times in the past 2
> years. I've been wondering about a good way to abstract this to have a
> library where you'd just plug your "business logic" and thus not have to
> care anymore about
Hi,
On Sat, Mar 3, 2012 at 10:38 AM, Gregory Collins wrote:
> Hi,
>
> The tutorial I gave for CUFP 2011 was a multi-user web chat program using
> the Snap Framework. STM channels make this kind of problem super-easy to
> deal with. Don't be afraid of forking lots of Haskell threads for programs
>
On Fri, Mar 2, 2012 at 5:19 PM, Paul Graphov wrote:
> Hello Cafe!
>
> I am trying to implement networked application in Haskell. It should
> accept many
> client connections and support bidirectional conversation, that is not
> just loop with
> Request -> Response function but also sending notifi
On Fri, Mar 2, 2012 at 7:34 PM, Joey Adams wrote:
> I'll try to put together a simple chat server example, like the one I
> wrote for stm-channelize.
Here it is:
https://github.com/joeyadams/haskell-chat-server-example
See, in particular, the serveLoop function. When a message is
received
Fri, Mar 02, 2012 at 07:34:41PM -0500, Joey Adams wrote
> On Fri, Mar 2, 2012 at 3:04 PM, Alexander V Vershilov
> wrote:
> > Hello, Paul.
> >
> > It seems you should not use 3 threads, but run in a data-driven behaviour
> > with
> > one thread per client.
>
> I don't think this will work for Pau
On Fri, Mar 2, 2012 at 3:04 PM, Alexander V Vershilov
wrote:
> Hello, Paul.
>
> It seems you should not use 3 threads, but run in a data-driven behaviour with
> one thread per client.
I don't think this will work for Paul's situation. He needs to be
able to send notifications to clients. This m
Hello, Paul.
It seems you should not use 3 threads, but run in a data-driven behaviour with
one thread per client.
You can take a look at network-conduit [1] example, there is a very good aproach
to tcp-network application. There are some iteratee based examples but they are
not so extensible.
[
Hello Cafe!
I am trying to implement networked application in Haskell. It should accept many
client connections and support bidirectional conversation, that is not
just loop with
Request -> Response function but also sending notifications to clients etc.
NB: I came from C++ background and used to
10 matches
Mail list logo
