RE: cvs: phpweb /include layout.inc /user css.php index.php
| From: | James Cox | Date: | Wed, 14 May 2003 21:08:44 +0000 |
| Subject: | RE: cvs: phpweb /include layout.inc /user css.php index.php | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-17667@lists.php.net to get a copy of this message | ||
>
> > we were making an extra apache request for _every_ page. even
> if it returns
> > 304, we still made the hit. when we push 100-250 reqs per
> second, like we do
> > when we're real busy, then an extra request for each 'real'
> apache request
> > is just insane.
>
> Well, with the changes made by Sascha (1.3->1.4) there would be no
> duplicate requests if the software involved supports "Cache-control". I
> thought this would solve the problem.
>
no, there would still be a request, of sorts.... the problem is that it's
completely redundant and it's too expensive.
> > The code still works, it only includes the css style if the
> ip2country stuff
> > works out. we eat a bit on it being cached... but then again,
> it's in every
> > header, so it'll work as the user browses around...
> >
> > if we get reports, investigate another method or ditch it, but i'm quite
> > confident that this works well enough now.
>
> OK, what do you think about some JS stuff? :) We have the cookie on the
> client side accessible for JS, so we can style the page accordingly
> without any explicit spec in the ouptout. I am planning to implement
> "search keyword" and "search option selection" remembering code the same
> way.
>
js is more than fine, as far as i am concerned.... passing off the
responsibility to the browser is fine. we just can't afford more processing
on the server till we optimize and improve what we have right now.
-- james