Hi Clif
On 8/7/26 16:40, Clif Flynt wrote:
Hi,
I'm moving my websites from Tclhttpd to Apache/Rivet. They are
all written using my Tcl-On-Track web framework.
Part of reworking Tcl-On-Track to run under Rivet is implementing
Direct_Url.
For those who don't use tclhttpd, Direct_Url is a mechanism to
allow a request like http://www.example.com/myProc to evaluate a
Tcl procedure "myProc" instead of throwing a 404 error. It's kind of
like a CGI script, but the procedure can be defined outside the
web data file hierarchy.
[...]
And, Finally-Finally, if anyone has a better suggestion than these hacks, I'm
all ears. At this point my Tcl-On-Track port if minimally functional. I need to
get a couple more features ported, and clean up a lot of exploratory code before
I release it.
My thanks to everyone who has put so much effort into Rivet.
Clif
For what I can understand from your goal description mod_rewrite is
exactly the functional component that fits into the problem: having URLs
expressed in some form (.du scripts included) mapped onto local paths
that can be handled by mod_rivet.
mod_rivet requires the file to be existing and the handled files are
defined in the configuration with the usual Apache configuration rules
https://tcl.apache.org/rivet/manual3.3/directives.html#id1340
handling also .du files would require to extend those rules by
generalizing mod_rivet selection in (src/mod_rivet_generator.c:69)
A solution that you may dislike as well (I would understand) could be
rewriting all .du URLs into .tcl
RewriteRule ^(.+)\.du$ $1.tcl
but that would require you also use aliases or symlinks to map those
local .tcl paths back into the local .du files. I didn't try if it works
and I don't like this du/tcl back and forth mapping either, I just can't
come up with anything smarter, given the current Rivet features and
limitations
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
