making the pearweb kitchen cooler
| From: | Pierre-Alain Joye | Date: | Fri, 04 Mar 2005 07:58:38 +0000 |
| Subject: | making the pearweb kitchen cooler | ||
| Groups: | php.pear.webmaster | ||
| Request: | Send a blank email to pear-webmaster+get-3932@lists.php.net to get a copy of this message | ||
Hello,
It seems that we do not have other choices to cut down some features
on the public part (as a first step).
This 1st step will use only static pages for all public pages.
Public pages mean pages where you do not need to be loged in to see
them.
A side effect is that you will loose some """features""" like the
username in the header, realtime numbers for various stats or having
to click 2 times to access a page.
I will process the pearweb section in this order:
- homepage
- groups/qa/news
- manual indeces
- packages index
- package homepage
- other (accounts,...)
This way php will not be involved at all to display datas that never
changes (never means not every single 10mins or hour).
My next step is to make the pkg downloads static. At least the first
try. That may require some changes in the installer. Mostly all
cases can be manage using static files or links on the server. If
one fails, the installer will use a rpc query to get a a download
url or an error.
The details may be discussed, but not the principles. Not like I am
a despot, but more that we do not have the choice. We have too much
success ;)
Regards,
--Pierre