9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How would you go about implementing this in Plan9?
Date: Fri, 10 Dec 2010 17:33:57 -0300	[thread overview]
Message-ID: <AANLkTimR5dvLqf9U_Ft9XSc7P2OBmJ1KA2KCbQJnNFQ+@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikU2tj_U5jdDqxJQttOo0YVQR9wdnh6Kb0hudGh@mail.gmail.com>

On Fri, Dec 10, 2010 at 5:01 PM, Eugene Gorodinsky
<e.gorodinsky@gmail.com> wrote:
> There's a lot more reasons for using one tab = one process approach. For
> chrome it really is a bargain. But for a non-browsing application it might
> not be so.
>

so the UI doesn't hang because webkit is single threaded, so you just
fork()/exec() a binary
and communicate via a named pipe?

in any case, like chrome, which uses some sort of shared bitmap for a
media player
the player could create and image and share it via nameimage(), then the decoder
program would just call namedimage() to get that one and draw to it...
hell it could draw directly to the display with image id 0 if you want
it, so really

for the im client a pipe is more than enough

--
Federico G. Benavento



  reply	other threads:[~2010-12-10 20:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10  9:34 Eugene Gorodinsky
2010-12-10  9:46 ` Lucio De Re
2010-12-10  9:58   ` hiro
2010-12-10  9:46 ` hiro
2010-12-10 10:01   ` Lucio De Re
2010-12-10 10:30 ` Charles Forsyth
2010-12-10 11:21   ` Eugene Gorodinsky
2010-12-11  1:43     ` Nathaniel W Filardo
2010-12-11 19:02       ` Eugene Gorodinsky
2010-12-10 15:52   ` David Leimbach
2010-12-10 20:01     ` Eugene Gorodinsky
2010-12-10 20:33       ` Federico G. Benavento [this message]
2010-12-11 19:01         ` Eugene Gorodinsky
2010-12-10 11:47 ` Federico G. Benavento
2010-12-10 13:23 ` erik quanstrom

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=AANLkTimR5dvLqf9U_Ft9XSc7P2OBmJ1KA2KCbQJnNFQ+@mail.gmail.com \
    --to=benavento@gmail.com \
    --cc=9fans@9fans.net \
    /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).