From: Nemo <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question about o/mero -> o/live event notification mechanism
Date: Tue, 1 May 2012 10:58:28 +0200 [thread overview]
Message-ID: <CC9890C7-9DD1-4B5F-817E-0F7770BFD5AF@lsub.org> (raw)
In-Reply-To: <op.wdlltlvd7pj5eq@thinkii>
On Apr 30, 2012, at 11:54 PM, aram wrote:
> Hi,
>
> i explore the UI of octopus and i try to understand how omero notifies the viewers for events.
> It is apparent from the documentation that the viewers "read" events from the ui/olive file.
> However, when i cat that file from the shell and "play" with a terminal a bit, i get no data.
> The terminals are updated correctly which indicates that the events are delivered.
> I checked the source of olive (port/live/live.b) and it simply reads (by calling updateproc(fd)) the file as expected.
>
> Obviously i am missing something important that the documentation does not cover.
> How can i read events posted by omero?
>
> Thanks
There are two type of events. IIRC.
User events like open, exec, ... are posted via o/ports, and you can
read them from there.
UI events are sent through a file with a protocol for o/live.
(Time ago they were sent also through ports, but I think I changed that).
The viewer reads a tree and then gets updates from that file.
That's internal and I don't think the man page describes that.
I can take a look to the source so I remember if you don't have luck
with these hints.
hth
next prev parent reply other threads:[~2012-05-01 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 21:54 aram
2012-05-01 8:58 ` Nemo [this message]
2012-05-02 13:56 ` aram
2012-05-02 15:02 ` Nemo
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=CC9890C7-9DD1-4B5F-817E-0F7770BFD5AF@lsub.org \
--to=nemo@lsub.org \
--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).