Hi,
I can write an asp app like this:
--------------------------------------------------------------
<%
## the top half of this file is where the bulk of my
## code and app logic lives. In the end it produces
## a data structure that represents what needs rendered
:
code
code
code
:
$my_struct = data that needs displayed on this page
%>
<some html>
<% render some of the page based on $my_struct %>
<some more html>
<some more html>
--------------------------------------------------------------
It would be nice if I could split it up like the following:
myapp.pl ## top half
myapp.asp ## bottom half
The file myapp.pl would just contain code, subroutines, logic for
the app, basically ending with creating a data structure.
The file myapp.asp would be the asp code/html to render the page
based on the data structure from the first file.
This means I could better serve our staff w/ DreamWeaver type tools,
and tell them to just edit the .asp files and leave the .pl files alone.
Couldn't Apache::ASP suck in a .pl file by the same name first if it
exists (and the conf file says to do so)?
-b
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
