ch00_09.htm:nmake.

[1]To see your ch01_01.htm:appropriate content.

[2]A ch01_01.htm:sequence of text lines.

[3]TCP/IP is a low-level Internet protocol for ch01_01.htm:video/mpeg (an MPEG stream).

[4]For more information about Internet ch01_01.htm:response data will start at the next line.[5]

[5]The ch01_01.htm:requests).[6]

[6]See Axioms of Web ch01_01.htm:string.[7]

[7]All scripts shown here generate plain text, ch01_02.htm:process is allowed to fork.

[8]In Chapter 24 we talk about ch01_03.htm:

[9]mod_vhost_alias offers similar functionality.

ch01_03.htm:

[10]Apache::RegistryNG and ch02_03.htm:apachectl must be root.

[11]Privileged ports are 0-1023. ch02_04.htm:following from a DOS prompt:

[12]See the Preface for more information about PPM ch02_05.htm:rwx------,[13] set the directory permissions to:

[13]See the ch02_05.htm:place under this directory. [14]

[14]You ch02_06.htm:will probably work without any modifications at all.

[15]Warnings and strict abort ch03_01.htm:

[16]MakeMaker allows easy, automatic ch03_01.htm:by using the APACHE_HEADER_INSTALL=0 parameter.

[17]%Config is defined in ch03_01.htm:will need to enable this option:

[18]See Chapters 8 and 9 of ch03_01.htm:[19]

[19]You might need the unstripped version for debugging ch03_03.htm:

[20]Apache::Cookie and ch03_09.htm:Perl directories.

[21]These files are run by the shell at startup and ch03_10.htm:HTTP/1.0, and then press the Enter key twice:

[22]If in doubt, try port 80, which is the standard ch04_02.htm:Apache::Registry handler looks like this:

[23]When we say ch04_02.htm:As dialog, depending on the client. [24]

[24]You can use ch04_02.htm:in the order in which they should be invoked.[25]

[25]It may ch04_02.htm:perl_destruct( )).[26]

[26]The parent ch04_04.htm:maintenance.[27]

[27]You may also find that mod_macro is ch04_04.htm:his own site:

[28]For complex ch06_02.htm:files.

[29]Don't forget ch06_08.htm:

[30]These are the recent pumpkins: Chip Salzenberg for 5.004, ch06_09.htm:won't be auto-flushed).[31]

[31]Buffering is ch06_12.htm:server that the request has been fully answered:

[32]This could perhaps be ch06_12.htm:touch" mode.[33]

[33]In your real code you ch09_02.htm:you can use the profiling tools.

[34]See Chapter 15 in the ch09_03.htm:

[35]You can tell top to sort the entries by ch09_05.htm:$ServerRoot/logs/dprof/$$[36] and run:

[36]Look ch10_01.htm:

[37]IV, for signed integer value, or a few other ch10_01.htm:

[38]PV, for pointer value (SV ch10_01.htm:

[39]Apache::Request is significantly faster than ch11_01.htm:dedicated to the mod_perl server?

[40]Of course, you also have ch11_01.htm:150 is close to optimal.[41]

[41]When we tried the same ch12_06.htm:

[42]The configuration directives we use are correct for Squid Cache ch12_07.htm:the client.[43]

[43]More details can be found at http://httpd.apache.org/docs/misc/fin_wait_2.html.

ch12_09.htm:server.

[44]See Section ch12_13.htm:(Total_RAM):

[45]4 MB of unshared memory is a ch17_02.htm:

[46]Disregard the fact that the actual password is stored in ch19_03.htm:this pseudocode:

[47]The ch20_01.htm:eventually your service will become unavailable.

[48]That is, database user ch21_01.htm:) exception-handling mechanism:[49]

[49]Notice the ch21_05.htm:correctly or not).[50]

[50]Perl 5.6.0 has introduced a new ch21_05.htm:presumably we intended).[51]

[51]For more ch21_05.htm:). Voilà—we have the date of one week ago!

[52]Perl folds the constants at compile ch21_05.htm:

[53]See also Class::Date and ch21_05.htm:current line:

[54]In Perl 5.8.0 use ch21_05.htm:breakpoint at this line.[55]

[55]Note that breakable lines of ch21_05.htm:expected.[56]

[56]You won't see the symbol ch21_08.htm:our example the match was successful.

[57]You should avoid using these at all, ch24_01.htm:incompatibilities in older Perl and Apache versions.

[58]Here ch24_04.htm:get the sources from:

[59]Perl 5.6.1 can be used with ch25_02.htm:pool, the temporary pool, and the server object:

[60]Pools are