Re: Rendering out a page

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 15645
interpreted = N
texte = >>How big of a page is this putting out? In my experience, WebCAt will >>through out the searches as fast as your server can serve the page. I'd >>be interested to know if this is true or not. > >Based on the 3 responses I will doing some testing over the weekend. >I think the issue is not the speed of webcat, but the fact that the person >browsing the page gets a feeling that a pure html doc loads faster. >Example.. >A page with approx 580 returned results on it where it has 10 embedded >searches within searches ie: >[search]1 > [search]3 > [search]3 > [/search]3 > to 10 searches > [/search]2 >[/search]1 > >Webcatalog does everything before displaying anything >An html page starts to load and display, and the user sees things on the >page immediately. Now the page is still loading it is just loading below >the visible window of there browser. So the feel is the page is faster, >where in fact webcatalog might have displayed the whole page faster, but >was slower at displaying just the first part of the page That is my take >on what is being reported to me. Now when the user backs up to this page >the search does not have to re-occur if it is rendered in html > >What brought this all on was converting a hand created page that is a total >pain in the butt to administer to webcat of an auto-cad drawing library we >keep with rev levels and all kinds of stuff. The multi data bases it looks >at total approx 3 megs of data. The person who administered this page is >on medical leave and I was asked to update it. One look at it and I put it >on webcat :) The people that use this page many many times a day claim it >is now slower. And they hate the page when it first set it up and used >[shownext]. The one thing in writing this response that popped into my head >was trying the [elapsedtime] tag and see what kind of numbers we are >generating. Again I am not saying webcat is slow by any means. What I am >saying is that on a complex search page it seems slow based on the way it >displays. Now this is not dial up users. This is over a 10-T lan. Keep >in mind that the autocad users that use this page are on PeeCee's and love >to shoot bullets at Mac's. So if I rendered the page back out to html I >can shut them up and have the ease of administration by using webcat :) Gary,There are several different WebDNA tasks that WILL slow down WebCat's page rendering -- and most definitely make the pages appear more slowly on the visitor's browser than if those pages were straight HTML. What your users are seeing may or may not be 'real', but to them it's real, because that's their 'perception' ... and that's all that matters.Why don't you put your WebCat code that creates the page using [writefile] into a protected admin form that lets YOU render a new page whenever you click the 'Render' button? This will make WebCat render the page 'on-demand' to straight HTML (the way they like it) and it still makes your updating process as simple and effortless as clicking a button ... :)Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://www.hui.net/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Rendering out a page (Kenneth Grome 1997)
  2. Rendering out a page-test results (grichter@panavise.com (Gary Richter) 1997)
  3. Re: Rendering out a page (grichter@panavise.com (Gary Richter) 1997)
  4. Re: Rendering out a page (Trevor Crist 1997)
  5. Re: Rendering out a page (John Hill 1997)
  6. Re: Rendering out a page (Grant Hulbert 1997)
  7. Rendering out a page (grichter@panavise.com (Gary Richter) 1997)
>>How big of a page is this putting out? In my experience, WebCAt will >>through out the searches as fast as your server can serve the page. I'd >>be interested to know if this is true or not. > >Based on the 3 responses I will doing some testing over the weekend. >I think the issue is not the speed of webcat, but the fact that the person >browsing the page gets a feeling that a pure html doc loads faster. >Example.. >A page with approx 580 returned results on it where it has 10 embedded >searches within searches ie: >[search]1 > [search]3 > [search]3 > [/search]3 > to 10 searches > [/search]2 >[/search]1 > >Webcatalog does everything before displaying anything >An html page starts to load and display, and the user sees things on the >page immediately. Now the page is still loading it is just loading below >the visible window of there browser. So the feel is the page is faster, >where in fact webcatalog might have displayed the whole page faster, but >was slower at displaying just the first part of the page That is my take >on what is being reported to me. Now when the user backs up to this page >the search does not have to re-occur if it is rendered in html > >What brought this all on was converting a hand created page that is a total >pain in the butt to administer to webcat of an auto-cad drawing library we >keep with rev levels and all kinds of stuff. The multi data bases it looks >at total approx 3 megs of data. The person who administered this page is >on medical leave and I was asked to update it. One look at it and I put it >on webcat :) The people that use this page many many times a day claim it >is now slower. And they hate the page when it first set it up and used >[shownext]. The one thing in writing this response that popped into my head >was trying the [elapsedtime] tag and see what kind of numbers we are >generating. Again I am not saying webcat is slow by any means. What I am >saying is that on a complex search page it seems slow based on the way it >displays. Now this is not dial up users. This is over a 10-T lan. Keep >in mind that the autocad users that use this page are on PeeCee's and love >to shoot bullets at Mac's. So if I rendered the page back out to html I >can shut them up and have the ease of administration by using webcat :) Gary,There are several different WebDNA tasks that WILL slow down WebCat's page rendering -- and most definitely make the pages appear more slowly on the visitor's browser than if those pages were straight HTML. What your users are seeing may or may not be 'real', but to them it's real, because that's their 'perception' ... and that's all that matters.Why don't you put your WebCat code that creates the page using [writefile] into a protected admin form that lets YOU render a new page whenever you click the 'Render' button? This will make WebCat render the page 'on-demand' to straight HTML (the way they like it) and it still makes your updating process as simple and effortless as clicking a button ... :)Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://www.hui.net/ Kenneth Grome

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:

emailer w/F2 (1997) math on date? (1997) [OT] RE: Drop down menu - Part 1 (2003) Webcatalog server support (1997) WebCatalog2 for NT Beta Request (1997) 2 easy questions re: [showif] and [sendmail] (1997) Hummm .... (2002) Sending E-mail (1997) Tab Charactor (1997) math context ignores date prefs? (1998) Conditional searching & displaying (1997) Re(8): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998) 2.0.1 new commands and contexts (1997) hideif glitch (2003) A little syntax help (1997) Um. silly question perhaps...but I don't know, so I'm askin'.. (2001) Some Questions (1997) Authenticate v6 (2004) Webcat+Webstar+Firesite - Encrypted Templates ? (2001) looking for some paid WebCatalog help (2000)