Eric S. Johansson wrote:
> that is one interpretation and one I had been trying to follow. The
> problem is that I'm taking everything below http://foo.com/ and
> using a CGI program to render the content the user will see. The
> first problem comes when trying to handle simple things like
> cascading style sheets. the CGI program gains control and the
> stylesheet is never seen.
How about using the configuration priorities here? Something like
this would be useful for you:
====
Directory / {
# Your configuration here..
}
Directory /icons {
Handler file
DocumentRoot /usr/share/cherokee/icons/
}
Directory /css {
Handler file
}
====
As long as the /icons and /css directory entries are behind the root
entry, it is going to have a higher priority.
> The second problem comes when you return different types of files.
> I need to replicate in my CGI program the file type to mime type
> association if I'm going to return files via the web server.
Yeah, it is something the server can not do for you in this case.
> The third problem is performance. Why should my CGI return files
> when the web server can do it much more quickly and efficiently?
I don't know! It seems a twisted configuration for me too, but it
seems like you want to do so.. :-) I'm still trying to figure out
what are you trying to set up.
> the need to do this is an artifact of the CGI environment. CGI is not a
> position to tell the web server what to do. maybe on the other hand, I
> should be looking at making my own module. One which embeds Python and
> implements the logic I want.
I have got a Python module, but it is unpublished by the moment. I
want to get the FastCGI stuff finished before releasing new
handlers, we should try to have just one instable component at a
time. :-)
--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
