Bug #17646 Updated: use only one version of each manual page
| From: | goba@php.net | Date: | Sat, 06 Jul 2002 16:37:23 +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-11178@lists.php.net to get a copy of this message | ||
ID: 17646
Updated by: goba@php.net
Reported By: mitja@doticni.net
-Status: Assigned
+Status: Closed
Bug Type: Website problem
Operating System: any
PHP Version: 4.2.1
Assigned To: goba
New Comment:
This thing is done, html directories are dropped from generation and
rsynced data...
Previous Comments:
------------------------------------------------------------------------
[2002-06-07 14:17:43] goba@php.net
That new virtual "print" directory is now actually there to half the
size of the manual files ;)) So this desire will be fullfilled. ;))
Another note on PHP scripts. If we introduce color coded PHP examples
(which would be quite nice IMHO), we need to put more PHP code into the
text part, so it would just get crappy with those HTML comments.
This bug can be closed, if the work is done on the printable versions,
and the html directories are dropped from the mirrored contents...
------------------------------------------------------------------------
[2002-06-07 13:29:27] mitja@doticni.net
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.
------------------------------------------------------------------------
[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.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/17646
--
Edit this bug report at http://bugs.php.net/?id=17646&edit=1