> Hi again-- > > On Wed, Nov 19, 2014 at 3:28 AM, Roberto De Ioris <[email protected]> > wrote: > >>> However, my question may have been unclear. My main - or at least >>> initial - objective is not to develop a uWSGI plugin for Racket, but a >>> Racket library that handles communication with the HTTP server using >>> the uwsgi protocol. Perhaps I misunderstand how uWSGI works, but I >>> think those are, or can be, two different things. >> >> Yes, tow different things, the procotol is named 'uwsgi' and it is >> described here: > > Okay, at least I have *some* idea of what is going on. Good to know. > >> http://uwsgi-docs.readthedocs.org/en/latest/Protocol.html > > Yes, as I stated in my initial message, I've read that, and that's > exactly why I'm confused. It describes only the packet encoding. Is > that really the entire protocol? What I am trying to understand is the > high-level message format. Is it simply a matter of encoding normal > HTTP messages in the uwsgi packet format? If so, I can certainly > handle that, but I don't find it at all obvious that that's what > should happen. And if there is some other message format, then I have > no idea what to do. > >> a fast parser in C is here: >> >> https://github.com/unbit/vpn-ws/blob/master/src/uwsgi.c#L9 > > Okay, I do see some hints here - the parser is looking for strings > like "QUERY STRING", and so on, but I cannot get a clear picture of > what is happening. I'm not much of a C programmer, but maybe if I read > it more thoroughly I can make some sense of it. What I think would > help more is to see some higher-level code that shows how an > application uses the parser. > > Anyway, thank you. I need to get some sleep. > > -- >
the protocol (like FastCGI and SCGI) transport a dictionary containing CGI variables. This is probably the step you are missing -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
