"John D. Leonard II" wrote:
>
> Joshua:
>
> > Note mixing in XMLSubs with HTML does not produce valid XML. If
> > you would like a pure XML approach, I would recommend looking into
> > XSLT which Apache::ASP also supports. In the latter case, the ASP
> > script and XSL template are processed a
Joshua:
> Note mixing in XMLSubs with HTML does not produce valid XML. If
> you would like a pure XML approach, I would recommend looking into
> XSLT which Apache::ASP also supports. In the latter case, the ASP
> script and XSL template are processed as ASP scripts, with the
> output XML used f
"John D. Leonard II" wrote:
>
> > For XMLSubs shorthand of this I might:
> > # httpd.conf
> > PerlSetVar XMLSubs my:header
> >
> > and then:
> > # global.asa, or my.pm, or My::Tags, which is used in global.asa
> > sub my::header {
> > $main::Response->Include('head.inc', @_);
> > }
> >
> For XMLSubs shorthand of this I might:
> # httpd.conf
> PerlSetVar XMLSubs my:header
>
> and then:
> # global.asa, or my.pm, or My::Tags, which is used in global.asa
> sub my::header {
> $main::Response->Include('head.inc', @_);
> }
>
> so I could finally:
>
>
How is performance w
Thanos Chatziathanassiou wrote:
>
> Since the question is on style, how about this:
> I am too bored to write navigational toolbars all the time, so once I have it
> once, in global.asa:
>
> sub head {
> my ($page,$title) = @_;
> return ''
>.' '
>.' src=
Since the question is on style, how about this:
I am too bored to write navigational toolbars all the time, so once I have it
once, in global.asa:
sub head {
my ($page,$title) = @_;
return ''
.' '
.' '
.''
.' '
.
"John D. Leonard II" wrote:
>
> All:
>
> In my never-ending search for ASP truth, I pose the following questions:
>
> 1) Should I gather subroutines common to several ASP files in the GLOBAL.ASA
> file, or should I put them in a PM file? Are there times when one method is
> preferable to anoth
