- 浏览: 27162 次
- 性别:
- 来自: 广州
最新评论
演示gen_event的运行过程:
mod_event_manager.erl:事件管理器:
mod_event_error_msg.erl: 错误日志事件:把错误放入对应的txt用。
mod_event_manager.erl:事件管理器:
mod_event_error_msg.erl: 错误日志事件:把错误放入对应的txt用。
%%%------------------------------------------------------------------- %%% @author zhongwencool@gmail.com %%% @copyright (C) 2014, <COMPANY> %%% @doc event manager center %%% %%% @end %%%------------------------------------------------------------------- -module(mod_event_manager). -author("zhongwencool@gmail.com"). %% API -export([start/0,start_link/0,stop/0,add_handler/2,add_sup_handler/2,del_handler/2]). -export([notify_error_msg/1,sync_notify_error_msg/0,call_open_file/0,call_close_file/0,which_handlers/0]). -define(SERVER, ?MODULE). %% @doc Creates a stand-alone event manager process, %% i.e. an event manager which is not part of a supervision tree and thus has no supervisor. start() -> gen_event:start({local,?SERVER}). %% @doc Creates an event manager process as part of a supervision tree %% @spec start_link() -> {ok, Pid} | {error, {alread_started,Pid}} start_link() -> gen_event:start_link({local,?SERVER}). stop() -> gen_event:stop(?SERVER). %% @doc Adds a new event handler to the event manager %%The event manager will call Module(Handler):init/1 to terminate the event handler. -spec add_handler(Handler,Args) -> ok | {'EXIT',Reason} | term() when Handler::Module | {Module,Id}, Args::term(), Module::atom(), Id::term(), Reason::term(). add_handler(Handler,Args) -> gen_event:add_handler(?SERVER,Handler,Args). %% @doc Adds a new event handler in the same way as add_handler/3 %% but will also supervise the connection between the event handler and the calling process. add_sup_handler(Handler,Args) -> gen_event:add_sup_handler(?SERVER,Handler,Args). %% @doc Deletes an event handler from the event manager:?MODULE %% The event manager will call Module(Handler):terminate/2 to terminate the event handler. -spec del_handler(Handler,Args) -> term() | {'EXIT',Reason} | {error,module_not_found} when Handler::Module | {Module,Id}, Args::term(), Module::atom(), Id::term(), Reason::term(). del_handler(Handler,Args) -> gen_event:delete_handler(?SERVER,Handler,Args). %% @doc 异步写入错误信息 notify_error_msg(Msg) -> gen_event:notify(?SERVER,{update_error_msg,Msg}). %% @doc 得到文件所有错误日志 sync_notify_error_msg() -> gen_event:sync_notify(?SERVER,{file_content}). %% @doc 重新找开储存错误文件:call要指定模块处理 %% 默认timeout 为5000ms call_open_file() -> gen_event:call(?SERVER,mod_event_error_msg,{open}). call_close_file() -> gen_event:call(?SERVER,mod_event_error_msg,{close},10000). %% @doc Returns a list of all event handlers installed in the event manager which_handlers() -> gen_event:which_handlers(?SERVER).
%%%------------------------------------------------------------------- %%% @author zhongwencool@gmail.com %%% @copyright (C) 2014, <COMPANY> %%% @doc line event %%% %%% @end %%% Created : 20. 二月 2014 下午2:30 %%%------------------------------------------------------------------- -module(mod_event_error_msg). -author("zhongwencool@gamil.com"). -behaviour(gen_event). %% API %% gen_event callbacks -export([init/1, handle_event/2, handle_call/2, handle_info/2, terminate/2, code_change/3]). -define(SERVER, ?MODULE). -record(state, {file_id ,file_name = "error_msg.txt"}). %%%=================================================================== %%% gen_event callbacks %%%=================================================================== %%-------------------------------------------------------------------- %% @private %% @doc %% Whenever a new event handler is added to an event manager, %% this function is called to initialize the event handler. %% %% @end %%-------------------------------------------------------------------- -spec(init(InitArgs :: term()) -> {ok, State :: #state{}} | {ok, State :: #state{}, hibernate} | {error, Reason :: term()}). init(FileName) -> process_flag(trap_exit, true), io:format("mod_event_error_msg: init:"), {ok, Fd} = file:open(FileName, [read, write]), {ok, #state{file_id = Fd,file_name = FileName}}. %%-------------------------------------------------------------------- %% @private %% @doc %% Whenever an event manager receives an event sent using %% gen_event:notify/2 or gen_event:sync_notify/2, this function is %% called for each installed event handler to handle the event. %% %% @end %%-------------------------------------------------------------------- -spec(handle_event(Event :: term(), State :: #state{}) -> {ok, NewState :: #state{}} | {ok, NewState :: #state{}, hibernate} | {swap_handler, Args1 :: term(), NewState :: #state{}, Handler2 :: (atom() | {atom(), Id :: term()}), Args2 :: term()} | remove_handler). handle_event(Event, State) -> NewState = do_handle_event(Event,State), {ok, NewState}. %%-------------------------------------------------------------------- %% @private %% @doc %% Whenever an event manager receives a request sent using %% gen_event:call/3,4, this function is called for the specified %% event handler to handle the request. %% %% @end %%-------------------------------------------------------------------- -spec(handle_call(Request :: term(), State :: #state{}) -> {ok, Reply :: term(), NewState :: #state{}} | {ok, Reply :: term(), NewState :: #state{}, hibernate} | {swap_handler, Reply :: term(), Args1 :: term(), NewState :: #state{}, Handler2 :: (atom() | {atom(), Id :: term()}), Args2 :: term()} | {remove_handler, Reply :: term()}). handle_call(Request, State) -> Reply = ok, NewState = do_handle_call(Request,State), {ok, Reply, NewState}. %%-------------------------------------------------------------------- %% @private %% @doc %% This function is called for each installed event handler when %% an event manager receives any other message than an event or a %% synchronous request (or a system message). %% %% @end %%-------------------------------------------------------------------- -spec(handle_info(Info :: term(), State :: #state{}) -> {ok, NewState :: #state{}} | {ok, NewState :: #state{}, hibernate} | {swap_handler, Args1 :: term(), NewState :: #state{}, Handler2 :: (atom() | {atom(), Id :: term()}), Args2 :: term()} | remove_handler). handle_info(_Info, State) -> {ok, State}. %%-------------------------------------------------------------------- %% @private %% @doc %% Whenever an event handler is deleted from an event manager, this %% function is called. It should be the opposite of Module:init/1 and %% do any necessary cleaning up. %% %% @spec terminate(Reason, State) -> void() %% @end %%-------------------------------------------------------------------- -spec(terminate(Args :: (term() | {stop, Reason :: term()} | stop | remove_handler | {error, {'EXIT', Reason :: term()}} | {error, term()}), State :: term()) -> term()). terminate(_Arg, _State) -> io:format("mod_event_line terminate:~p:::State:~p~n",[_Arg,_State]), ok. %%-------------------------------------------------------------------- %% @private %% @doc %% Convert process state when code is changed %% %% @end %%-------------------------------------------------------------------- -spec(code_change(OldVsn :: term() | {down, term()}, State :: #state{}, Extra :: term()) -> {ok, NewState :: #state{}}). code_change(_OldVsn, State, _Extra) -> {ok, State}. %%%=================================================================== %%% Internal functions %%%=================================================================== do_handle_event({update_error_msg,Msg},#state{file_id=Fd} = State) -> io:format(Fd,"~p~n",[Msg]), io:format("success write msg to file:~p",[Msg]), State; do_handle_event({file_content},#state{file_id=_Fd,file_name = FileName} = State) -> case file:read_file(FileName) of {ok,ErrorMsg} -> io:format("file_content:~p~n",[ErrorMsg]); {error,Reason} -> io:format("file consult error:~p~n",[Reason]) end, State; do_handle_event(Msg,#state{file_id=_Fd} = State) -> io:format("mod_event_error_msg:cannot handler_event this msg :~p",[Msg]), State. do_handle_call({open},State = #state{file_id=0,file_name = FileName}) -> {ok, NewFd} = file:open(FileName, [append,write]), io:format("open file :~p success~n",[FileName]), State#state{file_id=NewFd}; do_handle_call({open},State = #state{file_name = FileName}) -> io:format("file :~p already opened~n",[FileName]), State; do_handle_call({close},State = #state{file_id = Fd}) -> file:close(Fd), State#state{file_id = 0}; do_handle_call(Msg,State) -> io:format("mod_event_error_msg:cannot handler_call this msg :~p",[Msg]), State.
发表评论
-
Erlang 简单的节点互连
2014-03-19 23:41 481自己写的游戏跨服初步构架,以后再一点点完善,先记下时间线哈。 ... -
简单erlang节点互连实验
2014-03-10 15:53 684如果erlang:节点test1,test2互连接: 1.节点 ... -
Erlang OTP gen_event (0)
2014-02-26 14:30 1137原英文文档:http://www.erlang.org/erl ... -
erlang efficient guide 3
2013-08-19 22:19 1053* 3 Common Caveats * 3常见 ... -
erlang efficient guide 2
2013-08-18 01:02 8242 The Eight Myths of Erlang Per ... -
fun还是如以前一样狂跩吊么?
2013-08-16 22:26 580fun这么好用。为什么老大在最近都说不要用? gen:cal ... -
emacs 的erlang-flymake
2013-08-14 15:15 1412emacs 设置erlang-flymake erlang- ... -
erlang ets
2013-07-22 23:08 1786参见:http://www.cnblogs.com ... -
erlang的编程规范
2013-03-26 17:17 1878Programming Rules and Conventio ... -
Erlang------Mnesia
2013-03-25 12:49 1656读erlang编程指南Mnesia笔记: 1.mnesia 是 ... -
进程环
2013-03-18 16:48 774编写一个程序,它生成N ... -
匿名函数fun
2012-12-15 16:12 763lists:map(fun/1,[1,2,3]). 小试匿名函 ... -
并发编程实战otp--open telecom platform 二
2012-10-10 23:17 1103第二章:Erlang语言精要。 shell 的启动参数h ... -
并发编程实战otp--open telecom platform 一
2012-10-10 23:16 11481.erlang 的进程模型: 并发的基本单位是进程, ... -
learn some erlang
2012-10-09 22:54 672Erlang has this very pragm ... -
erlang语句块的简洁使用
2012-09-25 22:48 629begin end语句块的简洁使用:问题描述:将一堆人 ... -
命令式编程语言的标杆
2012-09-25 09:47 641命令式编程语言的标杆: 1.进程必须是语言的核心; 2.任何进 ... -
emacs与erlang的完美结合
2012-09-23 22:48 12331.在emacs中使用c+x c+z 启动erlang she ...
相关推荐
erlang_otp_win64_25.0
是erlang_otp_20.3 的win64安装包,内为exe文件,一路next即可安装完成 是适用于多线程、分布式开发的语言,也是如rabbitmq等重要工具的必须品 使用前需要配置环境变量:1.变量名为ERLANG_HOME,变量值为安装Erlang...
Erlang otp_src_20.3.tar.gz linux centos otp-OTP-20.0.tar.gz 可兼容rabbitmq3.7.0
erlang_otp_20.3_man开发手册,erlang_otp_20.3_man开发手册,erlang_otp_20.3_man开发手册
erlang-gen_tcp手册,详细完整,网络tcp开发好东东
本资源是 适用于 linux centos 的 最新版 otp_src_21.3.tar.gz
Erlang opt_win64 20.2 windows exe 安装包 Erlang 20.2 is the upcoming version of Erlang For Windows x64 installer 截至2018.01.25 groovy最新最稳定版本
erlang官网下载速度太慢了,无法忍受,erlang_otp_src_22.3.tar.gz+rabbitmq-server-3.8.3-1.el6.noarch.rpm
otp_win64_22.1的官方地址下载太慢,共享一下otp_Erlang_win64_22.1百度云下载地址
此文件为otp_src_20.2.tar.gz 的二次压缩文件 解压先用unzip otp_src_20.2.zip 出来, 然后就是安装时的 tar -zxvf otp_src_20.2.tar.gz内容了, 此文件为了自己使用是方便找到,请把分数定为1分,谢谢
Erlang otp_win64_21.2.exe是目前Erlang otp win64位的最新版本。
Erlang otp_win64_22.0.exe
erlang_otp_22.2_win64.exe & rabbitmq-server-3.8.3.exe
Erlang otp_win64_20.1.exe是当前最新版本的,更新时间2017-10-26
Erlang_OTP_设计原理 中文版 对erlang otp的讲解很 透彻
erlang-otp_mibs-19.3.6.4-1.el7.x86_64.rpm
Erlang是一种通用的面向并发的编程语言,它有瑞典电信设备制造商爱立信所辖的CS-Lab开发, 目的是创造一种可以应对大规模并发活动的编程语言和运行环境。
erlang 22.3版本 erlang_otp_src_22.3 安装说明https://blog.csdn.net/tangcv/article/details/111841082
Erlang_OTP_设计原理
最新版windows Erlang otp_win64_22.3.exe