[Bese-devel] Re: ucw 0.3.6pre1

Alan Shutko ats at acm.org
Tue Feb 8 16:29:20 UTC 2005


rm at fabula.de writes:

>  - this probably means that part of the "website/app" resides close to
>    the ucw application (whereever TALs et.al. are put) and another part
>    is within the (virtual) servers document root. I kind of like the idea
>    of keeping an application in one place (like tomcats WEBAPP).

Actually, I was hoping to avoid that problem.  If UCW can generate the
right httpd.conf entries for an application (as Tomcat can do for
mod_jk or whatever the current connector is), it should be able to
specify by specific pages what goes where.  

>  - Apache's delegation to a handler can be either URL based (with
>  the Location directive) orfile system path based (which doesn't
>  really work for dynamic content as is the case with mod_lisp). How
>  should Apache "know" that the request for /ucw/examples/index.ucw
>  needs to be send to the mod_lisp peer but
>  /ucw/examples/stylesheet.css not?

Ideally, I'd have the httpd.conf snippet specify what pages are static
and what pages go to a handler.  Probably by full URLs.

-- 
Alan Shutko <ats at acm.org> - I am the rocks.
The dough NEVER stops here.



More information about the bese-devel mailing list