Bug #17646 Updated: use only one version of each manual page
| From: | mitja at doticni dot net | Date: | Fri, 07 Jun 2002 17:29:27 +0000 |
| Subject: | Bug #17646 Updated: use only one version of each manual page | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-10731@lists.php.net to get a copy of this message | ||
ID: 17646
Updated by: mitja@doticni.net
Reported By: mitja@doticni.net
Status: Open
Bug Type: Website problem
Operating System: any
PHP Version: 4.2.1
New Comment:
Well, considering frequency of access, you might be right.
For a real answer, we would need to take a look at the statistics and
measure both ways, which is obviously too much work for so little
difference (it is probably little difference in any case).
Anyway, my request is one copy of each manual page instead of two, how
exactly it is done is not that important.
Previous Comments:
------------------------------------------------------------------------
[2002-06-07 12:52:27] goba@php.net
Well, I don't know really what takes more time (in sum):
a) error redirection on [the less used] printed pages, and PHP parsing
on all of them
b) error redirection on [the much more frequently used] "normal" manual
pages, and [slightly] more badwidth needed to send out printed
versions
I still think that a) is nicer, also counting on the error redirections
(more work on the server), not just HTML file size...
------------------------------------------------------------------------
[2002-06-07 12:47:27] mitja@doticni.net
So the printable version doesn't need to get PHP-processed, but can be
just sent away.
The amount of code would also be very low - my guess is around 300
bytes a file.
------------------------------------------------------------------------
[2002-06-07 12:37:23] goba@php.net
I still cannot see the point in putting PHP code deep into HTML
comments... Why to serve PHP code in HTML comment (more bandwith when
serving HTML files alone), and making it harder to recognize the PHP
code? Even as the non-printed manual pages are used much more often,
then the HTML versions. So IMHO the PHP format should be a base, and
not the HTML one.
------------------------------------------------------------------------
[2002-06-07 12:26:28] mitja@doticni.net
After #17644 is done, the manual pages could be reworked so that only
one page per language is needed, instead of two (print/non-print).
I suggest this is done so that the printable version is seen when the
file is passed straight to browser (something.html), and the
displayable version is shown when the same file is processed through
PHP. Something like this:
<!--<? manualHeader(...); if ($print) { ?>-->
print-only stuff
<!--<? } ?>-->
stuff common to both
<!--<? if (!$hidenotes) { ?>-->
notes
<!--<? } manualFooter(...); ?>-->
Then, non-existing directories could be used for the displayable
version, which would pass the request through error.php, which would
include the neccesary logic.
This would cut the number of files on the site in half, and the disk
space requirements for a mirror (together with #17644) even more.
Additionally, it would be easy to both show and not show notes in the
printable layout, again with using no additional files on the servers.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=17646&edit=1