Re: [SMARTY] CVS version
| From: | Monte Ohrt | Date: | Fri, 07 Jun 2002 15:46:59 +0000 |
| Subject: | Re: [SMARTY] CVS version | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-4688@lists.php.net to get a copy of this message | ||
I thought about that before, but concluded that it shouldn't be Smarty's responsibility. Handle that at your application level, or even better at the web server level. For instance, mod_gzip sends that header anyways, especially since it changes the size of the content.
Thoughts?
Alain Fontaine wrote:
Hi again, Read on www.web-caching.com: "Generate Content-Length response headers. It's easy to do, and it will allow the response of your script to be used in a persistent connection. This allows a client (whether a proxy or a browser) to request multiple objects on one TCP/IP connection, instead of setting up a connection for every request. It makes your site seem much faster." Wouldn't it be nice if Smarty could also send this header? -----Message d'origine----- De : Monte Ohrt [mailto:monte@ispi.net] Envoye : vendredi 7 juin 2002 17:33 A : Alain Fontaine Cc : smarty-general@lists.php.net Objet : Re: [SMARTY] CVS version On the first hit the cache must have been generated. The second hit used the cache and sent the Last-Modified header. Alain Fontaine wrote:-- Monte Ohrt <monte@ispi.net> Director of Technology, ispi Inc.Hello, Here is the output of a couple of consecutive CURL calls: <-- snip -->...