> On Thu, Mar 3, 2011 at 1:24 PM, Roberto De Ioris <[email protected]> wrote:
>>
>> Il giorno 03/mar/2011, alle ore 12.43, luigi scarso ha scritto:
>>
>>> erlang -> uwsgi  seem to work now also with short names (with latest
>>> dev):
>>>
>>> (uwsgierlang@johnII)80> {useless_atom,'uwsginode@johnII'} Â ! "Hello!"
>>> .
>>> "Hello!"
>>>
>>> and in the uwsgi terminal
>>> From: uwsgierlang@johnII To:  ��?��ŷC RegName: useless_atom
>>> eversion: 131
>>> etype: 107/k esize: 6
>>> string: Hello!
>>>
>>> I have this callback but it doesn't seem to work;
>>>
>>> def erlang_node_callback (arg):
>>> Â Â print "received an erlang message"
>>> Â Â print str(arg)
>>> uwsgi.erlang_func = erlang_node_callback
>>>
>>> What is wrong ?
>>>
>>>
>>
>>
>> Current implementation misses two part (already developed, i only need
>> to clean the code a bit).
>>
>> You can receive 3 kind of messages:
>>
>> rpc (working)
>> registered (uncommitted)
>> unregistered (uncommitted)
> ok, in the meanwhile I will use rpc
>
>
Just committed the registered process part.
# in python
def my_erlang_dumper(message):
print message
uwsgi.erlang_register_process("pydumper", my_erlang_dumper)
# in erlang
{ pydumper, 'nodename'} ! Message.
Processes must be registered in the master (this limit will be probably
removed in the future), so you cannot register them during http request
Request to unregistered process will only dump the message.
uwsgi.erlang_func is still unimplemented
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
