[erlang-questions] Clarify: HiPE auto-spawning?
Philip Robinson
chlorophil@REDACTED
Sat Nov 17 13:22:57 CET 2007
Previous message (by thread):
[erlang-questions] Clarify: HiPE auto-spawning?
Next message (by thread):
[erlang-questions] hi ulf! i've seen u already answered some questions related to the gen_event behaviour and its functions. since i'm new to erlang i'd like to ask a question related to that topic and i'm grateful for any reply. currently i'm implementing a logging system using gen_event and the syslog-interface to log additional local facilities to the linux sysklog-daemon. 1.) should my event-manager have a supervised handler for each facility and/or for each severity to enforce concurrency or is it better to have all events handled after one another by only one handler and using clauses to match certain conditions? 2.) when 'notifying' i assume the event-manager propagates the event to all handlers belonging to that manager. shouldn't i use 'call' instead to already specificly adress the certain handler with my request/event in order to avoid passing-around-messages and matching against clauses in each handler and therefore conserve performance? i'm still not very sure which approach makes the most sense, maybe you can give me a hint or two on how this is realized. thanx a lot for your time, gen_event + syslog + sysklogd
Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Thank you all. Your explanations are greatly appreciated. Cheers, Philip
Previous message (by thread):
[erlang-questions] Clarify: HiPE auto-spawning?
Next message (by thread):
[erlang-questions] hi ulf! i've seen u already answered some questions related to the gen_event behaviour and its functions. since i'm new to erlang i'd like to ask a question related to that topic and i'm grateful for any reply. currently i'm implementing a logging system using gen_event and the syslog-interface to log additional local facilities to the linux sysklog-daemon. 1.) should my event-manager have a supervised handler for each facility and/or for each severity to enforce concurrency or is it better to have all events handled after one another by only one handler and using clauses to match certain conditions? 2.) when 'notifying' i assume the event-manager propagates the event to all handlers belonging to that manager. shouldn't i use 'call' instead to already specificly adress the certain handler with my request/event in order to avoid passing-around-messages and matching against clauses in each handler and therefore conserve performance? i'm still not very sure which approach makes the most sense, maybe you can give me a hint or two on how this is realized. thanx a lot for your time, gen_event + syslog + sysklogd
Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the erlang-questions mailing list