Re: Webcat XML/XSLT Performance vs. static Html - Anyone from

This WebDNA talk-list message is from

2006

It keeps the original formatting. numero = 66271
interpreted = N
texte = After careful consideration we decided to work with webcat's xsl/xml features. Thanks for the solution though. In our case the product dbs are getting updated all the time, since they are updated by the users. Therefore, we have to keep the script writing down to as little resources as possible. So far everything is working great, still developing though. I have automatically generated a pool of xml files that are current with db content, and also an xsl/template file to display them. My template is global, therefore for future changes will be easy to update, and my xml files are written by an include. Although I am not entirely webdna free the amount of control given is worth it. I did ponder using actual web standard xml/xsl files, but was worried about browser compatibility, therefore also having to rely on webcat to parse these files into html, rather than having to rely on the enduser's browser.Thanks again.Adam OKenneth Grome wrote:>> In my case I would have 30-50k xml files sitting on the >> server being displayed by one xsl template/stylesheet, via the >> details.tpl file. When a user selects an item, they would be directed >> to the details.tpl file which would grab the correct xml file as a >> data source.>>>> As I had said earlier, I really would like to do this, but before >> diving in I need to know how much more resource intense this would be >> vs. using static html pages. Roughly speaking, lets say that the >> server will have to do this function approx 150-200 times a minute.>> >>> Naturally this would require more webdna processing time than if you just use static html pages. If your goal is to reduce the webdna processing requirements as much as possible, this is what I would do:>> 1- Write a script that makes webdna generate your static pages "on demand" by the admin, and run it only when you change your products database. This script would put a big but temporary (probably only a minute or two) load on webdna and the server, so I'm presuming that you are not updating your products database all the time.>> 2- Use a suffix in these static pages that Apache will serve directly, without involving webdna at all. This means your detailed product pages will NEVER AGAIN slow webdna down.>> 3- Use cookies to maintain the visitor's cart value. You'll have to, since you won't be able to pass the cart value to your static detail pages anyways from now on ... :)>>> I think that's the best you can do in terms of reducing the load on the webdna application.>> Regarding the use of cookies to store your cart values, from what I can tell hardly anyone turns cookies off these days anyways so using them to maintain the cart value should be fine. Another benefit of this approach is that webdna code is faster and easier to write when you do not have to pass the cart value in every link and form throughout the entire site ... :)>>> I think the bottom line here is that if you need or want the xls/xml stuff then go ahead and try the XSLT approach. But if you really don't need it, and especially if your goal is to reduce the load on webdna as much as possible, using the above outlined technique would be a better approach.>> The only negative feature I can think of regarding this approach is that it will take more space on the server's hard drive, because all those static html pages will (I believe) be bigger than their corresponding xml files. So if storage space is limited on your server this might be another thing to consider ...>> Sincerely, > Kenneth Grome > owner@kengrome.com> kengrome@gmail.com> www.kengrome.com>>>>>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/> -------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Webcat XML/XSLT Performance vs. static Html - Anyone from ( Adam O'Connor 2006)
Re: Webcat XML/XSLT Performance vs. static Html - Anyone from ( Kenneth Grome 2006)
Re: Webcat XML/XSLT Performance vs. static Html - Anyone from ( Adam O'Connor 2006)

After careful consideration we decided to work with webcat's xsl/xml features. Thanks for the solution though. In our case the product dbs are getting updated all the time, since they are updated by the users. Therefore, we have to keep the script writing down to as little resources as possible. So far everything is working great, still developing though. I have automatically generated a pool of xml files that are current with db content, and also an xsl/template file to display them. My template is global, therefore for future changes will be easy to update, and my xml files are written by an include. Although I am not entirely webdna free the amount of control given is worth it. I did ponder using actual web standard xml/xsl files, but was worried about browser compatibility, therefore also having to rely on webcat to parse these files into html, rather than having to rely on the enduser's browser.Thanks again.Adam OKenneth Grome wrote:>> In my case I would have 30-50k xml files sitting on the >> server being displayed by one xsl template/stylesheet, via the >> details.tpl file. When a user selects an item, they would be directed >> to the details.tpl file which would grab the correct xml file as a >> data source.>>>> As I had said earlier, I really would like to do this, but before >> diving in I need to know how much more resource intense this would be >> vs. using static html pages. Roughly speaking, lets say that the >> server will have to do this function approx 150-200 times a minute.>> >>> Naturally this would require more webdna processing time than if you just use static html pages. If your goal is to reduce the webdna processing requirements as much as possible, this is what I would do:>> 1- Write a script that makes webdna generate your static pages "on demand" by the admin, and run it only when you change your products database. This script would put a big but temporary (probably only a minute or two) load on webdna and the server, so I'm presuming that you are not updating your products database all the time.>> 2- Use a suffix in these static pages that Apache will serve directly, without involving webdna at all. This means your detailed product pages will NEVER AGAIN slow webdna down.>> 3- Use cookies to maintain the visitor's cart value. You'll have to, since you won't be able to pass the cart value to your static detail pages anyways from now on ... :)>>> I think that's the best you can do in terms of reducing the load on the webdna application.>> Regarding the use of cookies to store your cart values, from what I can tell hardly anyone turns cookies off these days anyways so using them to maintain the cart value should be fine. Another benefit of this approach is that webdna code is faster and easier to write when you do not have to pass the cart value in every link and form throughout the entire site ... :)>>> I think the bottom line here is that if you need or want the xls/xml stuff then go ahead and try the XSLT approach. But if you really don't need it, and especially if your goal is to reduce the load on webdna as much as possible, using the above outlined technique would be a better approach.>> The only negative feature I can think of regarding this approach is that it will take more space on the server's hard drive, because all those static html pages will (I believe) be bigger than their corresponding xml files. So if storage space is limited on your server this might be another thing to consider ...>> Sincerely, > Kenneth Grome > owner@kengrome.com> kengrome@gmail.com> www.kengrome.com>>>>>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/> -------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Adam O'Connor

DOWNLOAD WEBDNA NOW!

Re: Webcat XML/XSLT Performance vs. static Html - Anyone from

2006

Top Articles:

Related Readings: