Re: Webcat XML/XSLT Performance vs. static Html
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66262
interpreted = N
texte = Thanks for all the comments. I am going to try out the xslt feature, I think it is the best solution for what we are looking for. WebDna @ Inkblot Media wrote: > And another thing to consider is if they sites you see serving products via > static HTML pages are actually doing this or are they mapping the .HTML ext > through the dynamic processor. We do this when clients do not want to see > .TPL but instead like the .HTML extension. > > I have found quite a few sites that look like they are using raw HTML pages > to later find out that they are actually parsing using PERL or another > language. > > Just something to consider. > > Ron > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of > Donovan Brooke > Sent: Tuesday, February 14, 2006 10:38 AM > To: WebDNA Talk > Subject: Re: Webcat XML/XSLT Performance vs. static Html > > Kenneth Grome wrote: > > >> On Tue, 14 Feb 2006 10:06:59 -0600, Donovan Brooke wrote: >> >> >>> Adam, you must have a lot of products, or a slow machine to have >>> > performance > >>> issues. And, if you do have a lot of products, doing static html pages for >>> the details seems mind boggling. >>> >> I don't see why. I always write scripts that generate static pages for >> > the search > >> engines. >> > > Well, this is different than what adam is requesting isn't it. > > > > My point is that creating, editing, deleting an xml file for 30K files every > time > a product is edited seems more combersome than recreating the product > database in > WebDNA's own internal RAM database. One could keep the SQL database and > simply > update the front end database (webDNA's own internal database) when products > are edited and deleted. > > Adam, I've never used the XML integration to that extent so maybe Scott > can provide some feedback. However, I am confident that instead of > mirroring > the SQL database with 30K XML files, that you could get better performance > by mirroring the SQL db with a WebDNA database. > > Just a thought. > > Donovan > > > > ------------------------------------------------------------- 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:
Thanks for all the comments. I am going to try out the xslt feature, I think it is the best solution for what we are looking for. WebDna @ Inkblot Media wrote: > And another thing to consider is if they sites you see serving products via > static HTML pages are actually doing this or are they mapping the .HTML ext > through the dynamic processor. We do this when clients do not want to see > .TPL but instead like the .HTML extension. > > I have found quite a few sites that look like they are using raw HTML pages > to later find out that they are actually parsing using PERL or another > language. > > Just something to consider. > > Ron > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of > Donovan Brooke > Sent: Tuesday, February 14, 2006 10:38 AM > To: WebDNA Talk > Subject: Re: Webcat XML/XSLT Performance vs. static Html > > Kenneth Grome wrote: > > >> On Tue, 14 Feb 2006 10:06:59 -0600, Donovan Brooke wrote: >> >> >>> Adam, you must have a lot of products, or a slow machine to have >>> > performance > >>> issues. And, if you do have a lot of products, doing static html pages for >>> the details seems mind boggling. >>> >> I don't see why. I always write scripts that generate static pages for >> > the search > >> engines. >> > > Well, this is different than what adam is requesting isn't it. > > > > My point is that creating, editing, deleting an xml file for 30K files every > time > a product is edited seems more combersome than recreating the product > database in > WebDNA's own internal RAM database. One could keep the SQL database and > simply > update the front end database (webDNA's own internal database) when products > are edited and deleted. > > Adam, I've never used the XML integration to that extent so maybe Scott > can provide some feedback. However, I am confident that instead of > mirroring > the SQL database with 30K XML files, that you could get better performance > by mirroring the SQL db with a WebDNA database. > > Just a thought. > > Donovan > > > > ------------------------------------------------------------- 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!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
webcat NT (1998)
en/decrypt problem (1999)
New WebDNA patches available on the DRC (2004)
RAM variables (1997)
shipCost (2000)
Up and running ... at last !! (1997)
CSS in HTML emails? (2003)
Secure Server (1997)
Problems appending to database (1997)
[LookUp] (1999)
WebCat2 - [format thousands] (1997)
search results (1998)
US Postal Service API (2007)
beta 6 on OSX wierdness | more (2000)
WebCatalog sales (1997)
Fuzzy on [url] context (1998)
SQL db type (2006)
Almost a there but..bye bye NetCloak (1997)
Dedicated hosting recommendations (2000)
Help formatting search results w/ table (1997)