unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: "soso" X update; xplay.git available
Date: Fri, 30 Nov 2007 16:44:34 +0100	[thread overview]
Message-ID: <87lk8f3fh9.fsf@chbouib.org> (raw)
In-Reply-To: 87y7cfyf0s.fsf@ambire.localdomain

Hi!

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> 2/ a small work-in-progress collection of client code
>    <http://www.gnuvola.org/wip/xplay.git> is also available.
>    most likely this will see sporadic activity as we gain
>    experience w/ both new code (see `io' in xplay/seriously.scm)
>    and new way of sharing work in progress (git).  any tips from
>    experienced async-i/o hackers or git users welcome!

FWIW, Guile-RPC[0] has some code to allow for asynchronous RPC handling,
on the server-side (see `serve-one-stream-request/asynchronous' in `(rpc
rpc server)').  The idea is to pass the RPC handler a continuation that
it must invoke to actually return the RPC result over the network.
Thus, RPC call can be decoupled from RPC return (e.g., you can have an
application-level scheduler that first schedules the RPC handler and at
some later point schedules the return continuation).

I guess continuation-passing style could also be used to implement
asynchronous calls on the client-side.

> of course, all this is to get to a new window manager.  figure of merit
> will be how little xplay must evolve to get there.  can't be far, can it?

At any rate, this and your framework to handle the X protocol look cool!

Thanks,
Ludovic.

[0] http://www.gnu.org/software/guile-rpc/



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2007-11-30 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 14:38 "soso" X update; xplay.git available Thien-Thi Nguyen
2007-11-30 15:44 ` Ludovic Courtès [this message]
2007-12-04 14:57   ` Thien-Thi Nguyen

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lk8f3fh9.fsf@chbouib.org \
    --to=ludo@gnu.org \
    --cc=guile-user@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).