Comments on: Modular caching with XSL and PHP http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/ So much time, and so little to do! Thu, 28 Aug 2008 20:17:00 +0000 http://wordpress.org/?v=2.5.1 By: Brittney http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-12 Brittney Sat, 23 Aug 2008 01:25:13 +0000 http://girsbrain.org/blog/?p=5#comment-12 Well OK then. Hello! Well OK then. Hello!

]]> By: James http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-11 James Fri, 22 Aug 2008 02:04:27 +0000 http://girsbrain.org/blog/?p=5#comment-11 Why yes, I do :) Why yes, I do :)

]]> By: Brittney http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-10 Brittney Thu, 21 Aug 2008 15:10:23 +0000 http://girsbrain.org/blog/?p=5#comment-10 Hi James. I'm short and from high school, and played the alto sax. Do you remember me? :) Hi James. I’m short and from high school, and played the alto sax. Do you remember me? :)

]]> By: James http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-9 James Sat, 24 May 2008 23:17:36 +0000 http://girsbrain.org/blog/?p=5#comment-9 "that’s not the good way of dealing with XSL transformations. Consider search engines, mobile devices and other stuff like text browsers e.g. Lynx. It lacks accessibility." I've only got it going on internal sites right now. If I ever put it on a public site, which I will be in the next 6 months, there will be some checks involved. That's another post down the road, though. “that’s not the good way of dealing with XSL transformations. Consider search engines, mobile devices and other stuff like text browsers e.g. Lynx. It lacks accessibility.”

I’ve only got it going on internal sites right now. If I ever put it on a public site, which I will be in the next 6 months, there will be some checks involved. That’s another post down the road, though.

]]> By: Matt http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-8 Matt Sat, 24 May 2008 16:07:41 +0000 http://girsbrain.org/blog/?p=5#comment-8 "Since I send XML to the client and let their browser handle the rendering it’s even more useless." - that's not the good way of dealing with XSL transformations. Consider search engines, mobile devices and other stuff like text browsers e.g. Lynx. It lacks accessibility. However, still thinking about caching static pages. It makes sense to me. Maybe I will find some examples in Java. Thanks for you opinion. “Since I send XML to the client and let their browser handle the rendering it’s even more useless.” - that’s not the good way of dealing with XSL transformations. Consider search engines, mobile devices and other stuff like text browsers e.g. Lynx. It lacks accessibility.

However, still thinking about caching static pages. It makes sense to me. Maybe I will find some examples in Java.

Thanks for you opinion.

]]> By: James http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-7 James Fri, 23 May 2008 21:13:35 +0000 http://girsbrain.org/blog/?p=5#comment-7 The problem with caching nearly full (X)HTML output is it basically nulls out the advantages of using XSL. Since I send XML to the client and let their browser handle the rendering it's even more useless. That's a good point on re-processing for forms, though. I haven't encountered a scenario where I needed to do that, but I'll work it out right now since I have the time. I'll edit my post with it. <strong>Edit:</strong> Thinking about it some, I don't really see it as an issue. Take, for example, a search page: the search query would be passed in as an argument to run_action so each query would get it's own cache file. If you're talking about, for example, a poll module on your site and you want to cache output until the user votes and then show them the results and cache that, then I would do it like this: create a "plugin" (or whatever your framework needs) so that the poll module is run independently of the action, <em>but</em> handle caching in the same way. So you run_action("index") and then run_action("poll") and insert the poll XML into the action XML. The problem with caching nearly full (X)HTML output is it basically nulls out the advantages of using XSL. Since I send XML to the client and let their browser handle the rendering it’s even more useless.

That’s a good point on re-processing for forms, though. I haven’t encountered a scenario where I needed to do that, but I’ll work it out right now since I have the time. I’ll edit my post with it.

Edit: Thinking about it some, I don’t really see it as an issue.

Take, for example, a search page: the search query would be passed in as an argument to run_action so each query would get it’s own cache file.

If you’re talking about, for example, a poll module on your site and you want to cache output until the user votes and then show them the results and cache that, then I would do it like this: create a “plugin” (or whatever your framework needs) so that the poll module is run independently of the action, but handle caching in the same way. So you run_action(”index”) and then run_action(”poll”) and insert the poll XML into the action XML.

]]> By: Matt http://girsbrain.org/blog/2008/05/modular-caching-with-xsl-and-php/#comment-6 Matt Fri, 23 May 2008 21:08:45 +0000 http://girsbrain.org/blog/?p=5#comment-6 There is no problem with caching data as XML files... But caching IMHO should be done at later stage. I mean saving nearly full (X)HTML output in cache files. Only one thing bothers me with this solution. How to skip and re-process parts of code which should be dynamic e.g. forms (validation) or other user interaction parts of website. Should be quiet complicated cause there are no released examples of live code on caching of XSLt in PHP. If you got any ideas, I am ready to listen. There is no problem with caching data as XML files… But caching IMHO should be done at later stage. I mean saving nearly full (X)HTML output in cache files. Only one thing bothers me with this solution. How to skip and re-process parts of code which should be dynamic e.g. forms (validation) or other user interaction parts of website.

Should be quiet complicated cause there are no released examples of live code on caching of XSLt in PHP.

If you got any ideas, I am ready to listen.

]]>