[ejabberd] Jabber-RPC module : architecture questions
eric at ohmforce.com
Tue Sep 11 20:32:05 MSD 2007
If I dare answer my own mail :
there is no iq registered, I have juste registered a route to my
module, aptly named rpc. ++ HOST ...
mod_rpc is gen_server basically because .... I started from mod_echo
which is gen_server, but it's not carved in stone (hence my questions ;)
Le 11 sept. 07 à 18:06, Eric Cestari a écrit :
> For the time being,
> - mod_rpc is gen_mod and gen_server, which means that I get only one
> process for mod_rpc and queries are queued on it (right ?)
> - mod_rpc_test, containing my functions, is just a plain module, with
> no behaviors. so my mult method is called in the mod_rpc process
> (right ?)
> Another approach, maybe :
> Is there an OTP/ejabberd-approved way of creating a process for each
> client RPC query without queueing to a specific process ?
> (pointers in ejabberd-trunk code welcome :)
> I expect my xmlrpc queries to be stateless, so I think going the
> gen_fsm way is useless ...
> I am still trying to get my head around it, so if you need
> precisions, please ask.
> ejabberd mailing list
> ejabberd at jabber.ru
More information about the ejabberd