From: aram <aram@privatdemail.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] Question about o/mero -> o/live event notification mechanism
Date: Tue, 1 May 2012 00:54:47 +0300 [thread overview]
Message-ID: <op.wdlltlvd7pj5eq@thinkii> (raw)
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
next reply other threads:[~2012-04-30 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 21:54 aram [this message]
2012-05-01 8:58 ` Nemo
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=op.wdlltlvd7pj5eq@thinkii \
--to=aram@privatdemail.net \
--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).