I read through http://axkit.org/wiki/view/AxKit/XSPGuide about caching
and everything else. So I put the example code in one of my XSP pages
to see if it would give me any improvements and I don't believe it did,
probably because I'm not doing it right. Or not looking in the right
place to see. I've been using ApacheBench to try an increase total
completed requests and requests per second. But there isn't any change
from when I have the code in or out. So is the ApacheBench a bad way to
judge the cache effect? Or is my coding wrong? I haven't found any
other examples from my web searching so any input or points in the right
direction to XSP caching would be greatly appreciated. Thank you
index.xsp
--------------
<?xml-stylesheet href="NULL" type="application/x-xsp"?>
<?xml-stylesheet href="/styles/main.xsl" type="text/xsl"?>
<xsp:page xmlns:xsp="http://www.apache.org/xsp/core/v1";
...
>
<xsp:logic>
sub has_changed { 0 }
sub cache_params {
my ($class, $r, $cgi) = @_;
return $r->args;
}
</xsp:logic>
...
Matt Sergeant wrote:
On 6-Apr-06, at 1:36 PM, Aaron Steager wrote:
[Thu Apr 6 11:17:33 2006] [warn] [client 192.168.2.211] [AxKit] fast
handler called for /index.xsp
XSP is never cached. You can cache the output of your XSP page, but it
still performs all the XSLT stages regardless of that.
See Caching in http://axkit.org/wiki/view/AxKit/XSPGuide
I hope to change that in the next release, whenever I get around to that.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Aaron Steager
Web Programmer
Intralot USA
402-473-1531
This message and any other attachments are intended only for the use of the
Recipient and may contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient, you are hereby notified that any
dissemination of this communication is strictly prohibited. If you have
received this communication in error, please erase all copies of the message
and its attachments and notify us immediately. Please be aware that any views
expressed by an individual within this message do not necessarily reflect the
views of the company.
Security Warning: Please note that this email has been created in the knowledge
that Internet email is not a 100% secure communications medium. We advise that
you understand and observe this lack of security when emailing us. INTRALOT INC
is neither liable for the proper and complete transmission of the information
contained in this communication nor for any delay in its receipt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
