> First, to Roberto, you are understanding perfectly.
Ok, then i suggest you to go with uWSGI @rpc.
While i always suggest using higher-level RPC technologies for the web,
like REST and friends, for low-level approaches the rpc uWSGI subsystem
really shines (fast, and practically non-existent memory overhead).
You will end with a frontend simple app (using gevent):
def part1():
output = uwsgi.rpc(node, "give_me_part1")
def part2():
output = uwsgi.rpc(node, "give_me_part2")
def part3():
output = uwsgi.rpc(node, "give_me_part3")
def application(env, start_response):
gevent.spawn(part1)
gevent.spawn(part2)
gevent.spawn(part3)
# wait for all of the output
gevent.join([part1, part2, part3])
...
return [part1output, part2output, part3output]
obviously it is only sample-code but should give you an idea on the path
to follow.
There are obviously other techniques, but for me uWSGi rpc is the fast and
easier to use (you export functions remotely with a simple decorator)
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
