> Maybe it's silly question, but anyway - applying routing rules solved
> problem with connecting via http client. But what if I would like to
> connect with RPC client (to http-socket = :9090) directly to uwsgi RPC
> server, ie like this
>
> s = xmlrpclib.ServerProxy('http://hostname:9090')
> print s.hello()
>
> Above example will generate error:
> --- no python application found, check your startup logs for errors ---
> [pid: 19553|app: -1|req: -1/9] IP-ADDR () {32 vars in 529 bytes} [Wed May
> 15 16:10:26 2013] GET /favicon.ico => generated 21 bytes in 0 msecs
> (HTTP/1.1 500) 1 headers in 57 bytes (0 switches on core 0)
>
> And on client side will be raised xmlrpclib.ProtocolError
>
XML-RPC is at the same protocol level of uwsgi-RPC
So you would need a XML-RPC to uwsgi-RPC translator (something pretty easy
to realize, but no-one ever asked for it).
So from the uwsgi point of view the pattern will became:
http parsing -> xmlrpc parsing -> rpc call -> xmlrpc translation -> http
response
while now you have
http parsing -> rpc call -> http response
while using uwsgi.rpc() you have
uwsgi parsing -> rpc call -> uwsgi response
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
