Re: Webstar / WebCat - Persistent Setting

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 48797
interpreted = N
texte = >WebStar4.5, WebCat4.5 Plugin, OS9.2 ....>>Under the WebStar Admin entry, Connections tab, there is an option to turn>on Use Persistent CGI Connection.>>Does WebCat / Server performance improve with this setting turned on or it>makes no difference? According to WebStar docs, the plugin / cgi must have>this capability before turning this feature on in WebStar.>>For the life of me, I cannot find it in WebCat docs if this feature should>be enabled for WebStar servers. Anyone out there has any idea?>>I have tried it On as well as off but was not able to see any significant>performance change (the box just serves HTML webcat files .... Graphics and>other multimedia content are from a second dedicated server). It does makes>a difference on the second dedicated graphics server, even though there is>no cgi running other then the standard WebStar ones.If you're only serving one html page at a time from your webdna server -- with all the images coming from a separate server -- there's no reason to have persistent connections turned on unless you're also serving .css or .js files from the same webdna server.But given the fact that you're using webdna, there's no reason to serve these files separately, since they can be served more efficiently by including them than by making the browser request them as separate files. So if you're serving these files separately, I would suggest that you [include] them instead from now on.Usually persistent connections is turned on when the images and html files come from the same server. When more than one file is served over the same connection to the same recipient, using persistent connections will reduce the overhead of building up and tearing down multiple connections, resulting in faster performance.But in your case you're not serving images from the save server, so I would suggest that you leave it off on the webdna server.The image server is a different story however, because in most cases your image server will be serving multiple images to the same recipient. In this case it definitely helps to have persistent connections turned on.-- Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development CenterCebu City, Philippines +63 (32) 255-6921Wholesale WebDNA programming for only $20 per hour!----------------------------------------------------------------------------------------------------------------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: Webstar / WebCat - Persistent Setting (Terry Nair 2003)
Re: Webstar / WebCat - Persistent Setting (Kenneth Grome 2003)
Webstar / WebCat - Persistent Setting (Terry Nair 2003)

>WebStar4.5, WebCat4.5 Plugin, OS9.2 ....>>Under the WebStar Admin entry, Connections tab, there is an option to turn>on Use Persistent CGI Connection.>>Does WebCat / Server performance improve with this setting turned on or it>makes no difference? According to WebStar docs, the plugin / cgi must have>this capability before turning this feature on in WebStar.>>For the life of me, I cannot find it in WebCat docs if this feature should>be enabled for WebStar servers. Anyone out there has any idea?>>I have tried it On as well as off but was not able to see any significant>performance change (the box just serves HTML webcat files .... Graphics and>other multimedia content are from a second dedicated server). It does makes>a difference on the second dedicated graphics server, even though there is>no cgi running other then the standard WebStar ones.If you're only serving one html page at a time from your webdna server -- with all the images coming from a separate server -- there's no reason to have persistent connections turned on unless you're also serving .css or .js files from the same webdna server.But given the fact that you're using webdna, there's no reason to serve these files separately, since they can be served more efficiently by including them than by making the browser request them as separate files. So if you're serving these files separately, I would suggest that you [include] them instead from now on.Usually persistent connections is turned on when the images and html files come from the same server. When more than one file is served over the same connection to the same recipient, using persistent connections will reduce the overhead of building up and tearing down multiple connections, resulting in faster performance.But in your case you're not serving images from the save server, so I would suggest that you leave it off on the webdna server.The image server is a different story however, because in most cases your image server will be serving multiple images to the same recipient. In this case it definitely helps to have persistent connections turned on.-- Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development CenterCebu City, Philippines +63 (32) 255-6921Wholesale WebDNA programming for only $20 per hour!----------------------------------------------------------------------------------------------------------------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/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: Webstar / WebCat - Persistent Setting

2003

Top Articles:

Related Readings: