Thanks for the reply, Roberto! However, is there a reason that I just don't get for MAX_HTTP_VEC to be directly linked to the size of `uss'? struct iovec iov[MAX_HTTP_VEC]; char uss[MAX_HTTP_VEC * 2]; I mean, I understand that each piece of an HTTP request is parsed into a different iovec, and that 128 should be plenty for those... but as I understood, the iovecs point into `uss'? MAX_HTTP_VEC would then limit it to 128 pieces (iovecs) of request at a time, and 128*2=256 bytes of (uwsgi-protocol) request altogether? Or am I misunderstanding things?
And by "robust" I don't mean "fully-featured" per se -- our app doesn't do anything fancy, just GETs and POSTs, not even response streaming or anything. Just something that I could depend on not to suddenly drop requests without response (I guess returning a 500 Infernal Server Terror would be kinder?)... no offense meant, of course! I fully understand uWSGI 1.3-snapshot2 isn't necessarily stable software and the onus is on me to choose the right tools. My current reasoning for using bare HTTP mode uWSGI was to have one less moving part in the system, and thus lighten the load on the server. As for this mysterious new solution... well, I will certainly stay tuned! :) Best, Aarni _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
