On Sun, Sep 02, 2001 at 10:49:42AM -0500, Ian Bicking wrote:
> I think this can be better than simply telling the web server to serve
> certain kinds of files, because it allows you to do complicated
> URL->filename mappings, and to implement your own security for file
> access. These situations have already come up on the list, and I
> could use this sort of functionality myself.
Much as I like having the web server serve static files, it is
incompatible with having Webware automatically supply the filename
extension.
Also, even though alternative webservers are great in theory, in
practice most professional deployments will probably have to use
Apache anyway, because they need access to other Apache features
like allow/deny based on client IP, rewriting, virtual hosts, having some
virtual hosts on the same IP be Webware and some not, etc. Unless we want to
port all of these features to another webserver.
--
-Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED])
http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
