From: "Remi Vanicat" <remi.vanicat@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] lablgtk2: receiving messages from network?
Date: Sun, 16 Apr 2006 00:54:49 +0200 [thread overview]
Message-ID: <6b8a91420604151554jb36f96aw789a8d42755c1add@mail.gmail.com> (raw)
In-Reply-To: <b5def3a40604151233q774da2d8q403d6048c861c006@mail.gmail.com>
2006/4/15, Ivan Matveich <ivan.matveich@gmail.com>:
> Dear ocaml users,
>
> I'm writing a gtk program that must receive data through a tcp
> connection and react to it immediately.
As someone already tell you, you could use the Glib.IO interface.
There is also equeue of Gerd Stolpman that is integrated with the Gtk
main loop, see
http://www.ocaml-programming.de/programming/equeue.html
(Sory for sending you this twice, the first time I forget to send it
on the list).
next prev parent reply other threads:[~2006-04-15 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 19:33 Ivan Matveich
2006-04-15 19:45 ` [Caml-list] " yoann padioleau
2006-04-15 20:10 ` Markus Mottl
2006-04-15 20:58 ` Eric Cooper
2006-04-15 22:54 ` Remi Vanicat [this message]
2006-04-16 22:28 ` Ivan Matveich
2006-04-16 23:45 ` Jacques Garrigue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b8a91420604151554jb36f96aw789a8d42755c1add@mail.gmail.com \
--to=remi.vanicat@gmail.com \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).