On Thursday 06 December 2001 12:11 pm, Tavis Rudd wrote: > This brings up a question I've been meaning to ask about adapters. > Do they set the HTTP response header or is that the responsiblity of > the AppServer, Response, etc? I couldn't find any code, where they > do this, but I also couldn't find anywhere that AppServer or > HTTPResponse do it either. All I found was HTTPResponse.setStatus() > (but I'm going from memory here ;) > > I prefer the AppServer and HTTPResponse being in charge of that as it > makes it easier to write things like an builtin HTTPServer.
HTTPResponse is in fact the keeper of all headers until delivery time. But I don't see how you could have a situation where an _http adapter_ is not ultimately responsible for making sure the right things are done with the http headers. For example, mod_webkit has to hand the headers over to Apache and it naturally lives in Apache not in the app server. Since a raw response contains the headers in a clearly delimited fashion, there should be no hang ups at all writing the builtin http server. In fact, if I remember right, they are already in standard http form and ready to be copied over. Plus AsyncHTTPServer already showed this being done. It was only the async part that didn't work out. I'm not sure what the mod_webkit problem is, but I seem to remember that Apache has internal redirects vs. external and it has to do with the look and feel of the Location header (I wish it was simply a different header instead!). -Chuck _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
