Hi,
Joerg, thanks for your comments, I eagerly await AxKit 2.0, until then I
guess I'll use a taglib to combine the functional components, as you
suggest.
In order to do this, could anyone tell me best way to make a taglib that
uses tags from another taglib?
For example, to get something like:
<mylib:query-my-db>
<!-- esql stuff here -->
</mylib:query-my-db>
to expand to:
<esql:connection>
<esql:driver>Pg</esql:driver>
<esql:dburl>dbname=axkit</esql:dburl>
<esql:username>postgres</esql:username>
<esql:password>password</esql:password>
<esql:execute-query>
<!-- esql stuff here -->
</esql:execute-query>
</esql:connection>
Regards
Adam
________________________________________________________
s_p_a_m_t_r_a_p from:[EMAIL PROTECTED]
Do not email the above address or remove these two lines
-----Original Message-----
From: Jörg Walter [mailto:[EMAIL PROTECTED]
Sent: 23 July 2003 11:44
To: [EMAIL PROTECTED]
Subject: Re: Building applications with AxKit and XSP, in a reusable
extensible way...
Am Wednesday, 23. July 2003 12:23, schrieb Adam Griffiths:
> Hi,
>
> I've been using AxKit for a while now and I'd really appreciate any
> ideas or information on the following question.
>
> XSP is great for generating dynamic XML documents and it's fast too.
> It also caches the Perl code necessary to generate the dynamic XML
> page so multiple requests only require it is parsed once. However as
> my application grows and has an increasing number of XSP pages I am
> finding that many share identical code / xsp-xml fragments, which
> makes maintaining them all is becoming increasingly difficult.
Use taglibs or XInclude. If you find yourself reusing similar functional
components, make a taglib of them. If you find yourself reusing data
components, or lots of data with a little bit of logic, use XInclude. If you
find yourself reusing a lot of data, try rearranging things so you do XSLT
_after_ XSP. Of course, this combination does not work with logic inside
your
data.
I use XSLT->XSP->... a lot, but as you already recognized, it's darn slow.
For the caching behaviour you suggest you will have to wait for AxKit 2.0.
It
will most probably have that flexibility.
--
CU
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
