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:
Encrypting the seed (2001)
Can't load tmpl files (1997)
Emailer file formats (1998)
Stopping NT WebCat service (1998)
Trouble Searching (1999)
emailer on Windows Beta 18 (1997)
FW: WebDNA-Talk searchable? (1997)
[shipCost] math formula? (1997)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
New Command prefs ... (1997)
More than one db with the same namn (was: WC2f3) (1997)
TCP Connect code for SMTP transaction (2004)
Sitebuilder (2004)
setting taxable to true (1997)
new storefront (2003)
Server IP address? (1998)
HELP WITH DATES (1997)
[WebDNA] Versions (2014)
Re:multiple digests, please stop (1997)
Still can't upgrade users.db to 2.1.1 (1998)