From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Nemo <nemo@lsub.org>
In-Reply-To: <op.wdlltlvd7pj5eq@thinkii>
Date: Tue,  1 May 2012 10:58:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC9890C7-9DD1-4B5F-817E-0F7770BFD5AF@lsub.org>
References: <op.wdlltlvd7pj5eq@thinkii>
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
Topicbox-Message-UUID: 82e63a22-ead7-11e9-9d60-3106f5b1d025


On Apr 30, 2012, at 11:54 PM, aram wrote:

> Hi,
>=20
> 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.
>=20
> Obviously i am missing something important that the documentation does =
not cover.
> How can i read events posted by omero?
>=20
> 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