Welcome to WebmasterWorld Guest from 54.196.243.192

Forum Moderators: httpwebwitch

Message Too Old, No Replies

is xsl superfluous if you have direct access to the db

     
7:39 am on Oct 27, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:July 24, 2002
posts:1124
votes: 0


a software providor of ours wishes to switch to xsl templating from php/mysql/smarty.

i have grasped the basics and had a look at the templates he already uses in another app.

at the moment we:

1) select data from database
2) run the php script to organise the data
3) echo the data in the smarty templates

if i understand correctly, if we switch to xsl templates we have to

1) select the data from the database
2) run the php script to organise the data
3) use this data to generate the xml
4) echo it out using xsl

this doesn't seem to me like a positive gain - rather an extra step. have i understood correctly?

are there any benefits to be gained by doing it this way?

many thanks
2:07 pm on Oct 27, 2010 (gmt 0)

Moderator This Forum from CA 

WebmasterWorld Administrator httpwebwitch is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Aug 29, 2003
posts:4059
votes: 0


Sounds like someone is really good with a hammer and wants everything else to be a nail.

It's more common for people to upgrade from XSLT to some other engine, because XSLT tends to perform poorly under heavy load. Popular ones are Smarty for PHP, and NVelocity for .NET

IMHO you're right, this isn't an upgrade, it's just a lot of refactoring ... and what's more it'll tax your CPU harder
4:59 pm on Oct 27, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:July 24, 2002
posts:1124
votes: 0


thanks for the insight. we need to rethink. especially as there will be some quite heavy load during peak shopping periods.
5:38 pm on Oct 27, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Dec 15, 2003
posts:2606
votes: 0


A good way to approach the discussion is to ask simple questions.

Why are we thinking of switching? (ie what is the goal)

Will switching achieve this goal?
-->If yes
----> Could switching cause new issues that outweigh the goal?
------>If yes
--------> perform proof of concept
-->If No
----> Then why switch?