[erlang-questions] How to force kernel application will always be started before my app

[Roger Critchlow]

I'd think that:

   an event that fired when Module:Function/Arity was called
   an event that fired when Module:Function/Arity returned
   an event that fired when Module:Function/Arity was aborted by an
exception

would cover a lot of cases.

-- rec --

On Tue, Nov 25, 2008 at 11:32 AM, Richard Carlsson <richardc@REDACTED>wrote:

> Vlad Dumitrescu wrote:
> > <thinking loud>
> > What I would like to have is a system-wide event source that would let
> > interested parties know when important events in the system take
> > place, like "kernel started", "code server started", "mnesia
> > started/stopped", but maybe also things like "node
> > connected/disconnected". This would mean that this service would need
> > to be started very early and other applications could register
> > themselves as event producers and/or listeners.
> >
> > Quite a large mechanism to put in place, but maybe it's interesting to
> consider?
>
> I recently discussed precisely such a thing with the OTP guys, and it
> seems like something that could be done for R13. The main work lies in
> listing the events important enough. (Presumably, it should be rather
> low-traffic things, so e.g. opening/closing files might be too much.)
>
> Do post your ideas. Here's my list so far:
>
>  - system services (and mnesia) started/stopped
>  - boot sequence completed
>  - node connect/disconnect
>  - module loaded
>  - any info reported by erlang:system_monitor(), unless the
>    user has redirected it to some other process
>  - (remote)shell started/terminated
>
>    /Richard
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20081125/94b5f321/attachment.htm>