Hi, Poirier
Thank u for your polite reply.
> Sorry, but our applications in production are deployed using FastCGI,
> memcached and supervisord. I don't have a practical experience of
> mod_wsgi.
No problem.
I gave up using Nagare with mod_wsgi and I tried to use Nagare with
FastCGI and memcached.
And I got an error which says:
File "/usr/local/nagare/lib/python2.5/site-packages/nagare-0.1.0-
py2.5.egg/nag
are/sessions/common.py", line 256, in set
self._set(session_id, cont_id, new_id, secureid, query_string,
*self._dumps(
data))
TypeError: _set() takes exactly 7 arguments (8 given)" while reading
response he
ader from upstream, client: #.#.#.#, server: localhost, request:
"GET /
HTTP/1.1", upstream: "fastcgi://
127.0.0.1:9000", host: "#.#.#.#"
I saw the source code and the _set function didn't do anything,
so I commented out the self._set line and there happened no error.
It's just an ad hoc, but I report it any way.
Now, I came across another problem in the end.
I bound an anchor link with a class's method using h.a's action
method.
When I run my app using Nagare's web server,
The class' method was called and a component was swapped to another
component as I intended.
But when I run my app using a webserver(nginx) and FastCGI(Nagare),
The class' method was NEVER called.
I'm wondering there is some shortage of FastCGI parameters or cookie,
but have no idea at all(I made sure that cookies were sent to Nagare
using tcpdump).
Could u give me some hint?
> In this domain, our plan is rather to integrate a complete events/
> tasklets based HTTP server with Nagare, that outperform the threaded/
> processes based ones.
I'm quite interested in running my apps fast and making it scalable,
so your idea sounds pretty attractive and I'm looking forward to
seeing the completion.
Thanks.