cvs: phpdoc /kr/features connection-handling.xml persistent-connections.xml remote-files.xml
| From: | WonHee Hwang | Date: | Wed, 10 Jan 2001 05:49:22 +0000 |
| Subject: | cvs: phpdoc /kr/features connection-handling.xml persistent-connections.xml remote-files.xml | ||
| Groups: | php.doc | ||
| Request: | Send a blank email to phpdoc+get-969333528@lists.php.net to get a copy of this message | ||
regina Tue Jan 9 21:49:22 2001 EDT
Modified files:
/phpdoc/kr/features connection-handling.xml
persistent-connections.xml remote-files.xml
Log:
Index: phpdoc/kr/features/connection-handling.xml diff -u phpdoc/kr/features/connection-handling.xml:1.2 phpdoc/kr/features/connection-handling.xml:1.3 --- phpdoc/kr/features/connection-handling.xml:1.2 Tue Jan 9 16:39:21 2001 +++ phpdoc/kr/features/connection-handling.xml Tue Jan 9 21:49:22 2001 @@ -1,13 +1,12 @@ - <chapter id="features.connection-handling"> + <chapter id="features.connection-handling"> <title>Connection handling</title> <note> - <para>The following applies to 3.0.7 and later.</para> + <para>ì´ ê¸°ë¥ì PHP version 3.0.7 ì´íë¶í° ì ì©ë ê²ë¤ì´ë¤.</para> </note> <para> - Internally in PHP a connection status is maintained. There are 3 - possible states: + ë´ë¶ì ì¼ë¡ PHPë ì°ê²°ì ìí를 ë¤ì 3ê°ì§ì¤ íëë¡ ì¤ì íë¤. : <itemizedlist> <listitem><simpara>0 - NORMAL</simpara></listitem> <listitem><simpara>1 - ABORTED</simpara></listitem> @@ -16,60 +15,55 @@ </para> <simpara> - When a PHP script is running normally the NORMAL state, is active. - If the remote client disconnects the ABORTED state flag is - turned on. A remote client disconnect is usually caused by the - user hitting his STOP button. If the PHP-imposed time limit (see - <function>set_time_limit</function>) is hit, the TIMEOUT state flag - is turned on.</simpara> + PHP ì¤í¬ë¦½í¸ê° ì¼ë°ì ì¼ë¡ ì¤íëê³ ìì ëë NORMAL ìíê° activeëë¤. + ë§ì½ ì격 í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëê²ëë©´ ABORTED ìí flagê° ì¼ì§ê² ëë¤. + ë³´íµ í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëë ê²ì ì¬ì©ìê° STOP ë²í¼ì ëë ì ë ì¼ì´ëë¤. + ë§ì½ PHPê° ì¤ì í ìê° ì íì (<function>set_time_limit</function>ì ë³´ë¼) ê±¸ë¦¬ê² ëë©´ + TIMEOUT ìí flagê° ì¼ì§ê² ëë¤. + </simpara> <simpara> - You can decide whether or not you want a client disconnect to cause - your script to be aborted. Sometimes it is handy to always have your - scripts run to completion even if there is no remote browser receiving - the output. The default behaviour is however for your script to be - aborted when the remote client disconnects. This behaviour can be - set via the ignore_user_abort php3.ini directive as well as through - the corresponding php3_ignore_user_abort Apache .conf directive or - with the <function>ignore_user_abort</function> function. If you do - not tell PHP to ignore a user abort and the user aborts, your script - will terminate. The one exception is if you have registered a shutdown - function using <function>register_shutdown_function</function>. With a - shutdown function, when the remote user hits his STOP button, the - next time your script tries to output something PHP will detect that - the connection has been aborted and the shutdown function is called. - This shutdown function will also get called at the end of your script - terminating normally, so to do something different in case of a client - diconnect you can use the <function>connection_aborted</function> - function. This function will return true if the connection was - aborted.</simpara> + ì¬ë¬ë¶ì í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëìì ë ì¤í¬ë¦½í¸ê° ìíì ì¤ë¨í ê²ì¸ê° ìëê°ë¥¼ ê²°ì íì¬ì¼ íë¤. + ëëë¡ ì격 ë¸ë¼ì°ì ê° ì´ë¤ ê²°ê³¼ë ë°ìë¤ì´ì§ ìëë¼ë ì¤í¬ë¦½í¸ë¥¼ ëê¹ì§ ì¤ííë ê²ì´ í¸ë¦¬í ëê° ë§ë¤. + 기본 ëìì í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëì¼ë©´ ì¤í¬ë¦½í¸ë ì¤ë¨ëë ê²ì´ë¤. + ì´ ëìì ignore_user_abortë¼ë php3.ini ì§ìì(directive)ë, + php3_ignore_user_abortë¼ë Apacheì .confì ì§ììë¡ ì¤ì ì´ ê°ë¥íê³ , + <function>ignore_user_abort</function> í¨ì를 ì¬ì©íì¬ ì¤ì í ìë ìë¤. + ë§ì½ PHPìê² ì¬ì©ìê° ë´ë¦° ì¤ì§ ëª ë ¹ì 무ìíë¼ê³ ë§í´ì£¼ì§ ììë¤ë©´, + ì¬ì©ìì ì¤ì§ ì í¸ë ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ë¥¼ ì¢ ë£ìí¨ë¤. + ë¨, <function>register_shutdown_function</function>ì ì¬ì©íì¬ + shutdown í¨ì를 ë±ë¡í´ ëì ê²½ì°ë ìì¸ê° ëë¤. + shutdown í¨ì를 ì¬ì©íë©´, ì¬ì©ìê° STOPë²í¼ì ëë ì ë, + ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ë ë¨ì ì¶ë ¥ì íë ¤ê³ íê³ , + PHPë ì°ê²°ì´ ì¤ë¨ëììì ì¸ì§íì¬ shutdown í¨ì를 í¸ì¶íê² ëë¤. + shutdown í¨ìë ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ê° ì ìì ì¼ë¡ ì¢ ë£ëìì ëë í¸ì¶ ëë¤. + ë§ì½ ì¬ê¸°ì í´ë¼ì´ì¸í¸ì ì°ê²° ì¤ë¨ ëì ì¼ë°ì ì¸ ì¢ ë£ìì ë¤ë¥¸ ëìì ìíë¤ë©´ + <function>connection_aborted</function> í¨ì를 ì¬ì©íë©´ ëë¤. + ì´ í¨ìë ì°ê²°ì´ ì¤ë¨ëìë¤ë©´ true를 ë°ííë¤. + </simpara> <simpara> - Your script can also be terminated by the built-in script timer. - The default timeout is 30 seconds. It can be changed using - the max_execution_time php3.ini directive or the corresponding - php3_max_execution_time Apache .conf directive as well as with - the <function>set_time_limit</function> function. When the timer - expires the script will be aborted and as with the above client - disconnect case, if a shutdown function has been registered it will - be called. Within this shutdown function you can check to see if - a timeout caused the shutdown function to be called by calling the - <function>connection_timeout</function> function. This function will - return true if a timeout caused the shutdown function to be called.</simpara> - + ì¤í¬ë¦½í¸ë ë´ì¥ë íì´ë¨¸ì ìí´ ì¢ ë£ë ì ìë¤. + 기본 timeout ìê°ì 30ì´ë¡ ëì´ ìë¤. + ì´ê²ì max_execution_timeì´ë¼ë php3.ini ì§ìì(directive)ë, + ëì¼í ë´ì©ì php3_max_execution_timeì´ë¼ë Apacheì .conf ì§ììì ìí´ + ë¤ë¥´ê² ì¤ì ì´ ê°ë¥íê³ <function>set_time_limit</function> í¨ì를 ì¬ì©íì¬ ì¤ì í ìë ìë¤. + ì¤ì í ìê°ì´ 경과íë©´ ì¤í¬ë¦½í¸ë ìëì¼ë¡ ì¤ë¨ëê³ , + ì´ ì¤í¬ë¦½í¸ë ìì ì¤ëª í í´ë¼ì´ì¸í¸ìì ì°ê²°ì´ ì¢ ë£ë ê²ì²ë¼ ëìíë¤. + ë°ë¼ì shutdown í¨ìê° ë±ë¡ëì´ ìë¤ë©´ ì´ í¨ìê° ì¤íëë¤. + shutdown í¨ìë´ìì ì´ í¨ìê° timeoutì ìí´ í¸ì¶ë ê²ì¸ê°ë¥¼ íë¨íë ¤ë©´ + <function>connection_timeout</function> í¨ì를 ì¬ì©íë©´ ëë¤. + ì´ í¨ìë timeoutì ìí´ shutdown í¨ìê° í¸ì¶ëìë¤ë©´ true를 ë°ííë¤. + </simpara> <simpara> - One thing to note is that both the ABORTED and the TIMEOUT states - can be active at the same time. This is possible if you tell - PHP to ignore user aborts. PHP will still note the fact that - a user may have broken the connection, but the script will keep - running. If it then hits the time limit it will be aborted and - your shutdown function, if any, will be called. At this point - you will find that <function>connection_timeout</function> - and <function>connection_aborted</function> return true. - You can also check both states in a single call by using the - <function>connection_status</function>. This function returns a - bitfield of the active states. So, if both states are active it - would return 3, for example.</simpara> + íê°ì§ ì ìí ì¬íì ABORTEDì TIMEOUT ìíë ë ê°ê° ëìì activeë ì ìë¤ë ê²ì´ë¤. + ì´ê²ì PHPê° ì¬ì©ì ì¤ë¨ì 무ìíëë¡ ì¤ì í´ ëìì ë ì길 ì ìë¤. + ë ë¤ë¥¸ ê²½ì°ë ì¬ì©ìê° ì°ê²°ì ëì§ë ììì§ë§ ì°ê²°ì ì´ë¤ 문ì ê° ì겨 ì°ê²°ì´ ë§ê°ì§ ê²½ì°ë¡, + ì´ë° ê²½ì°ì ì¤í¬ë¦½í¸ë ê³ìì¤íëê³ , ìê° ì íì ê±¸ë ¤ ì¤í¬ë¦½í¸ì ìíì´ ì¤ë¨ëê³ shutdown í¨ìê° í¸ì¶ëë©´, <function>connection_timeout</function>ê³¼ <function>connection_aborted</function>í¨ì 모ë true를 ë°ííê² ëë¤. + ì¬ë¬ë¶ì <function>connection_status</function> í¨ì를 ì¬ì©íì¬ ëê°ì§ ìí 모ë를 ê²ì¬í ì ìë¤. + í¨ìë ê° ìíì ëí ì 보를 bitë¨ìë¡ ê°ì§ê³ ìë¤. + 를ë¤ì´ ììê°ì´ ABORTì TIMEOUT ë ê°ì ìíê° ëª¨ë activeëì´ ìë¤ë©´ ì´ í¨ìë 3ì ë°ííë¤. + </simpara> </chapter> Index: phpdoc/kr/features/persistent-connections.xml diff -u phpdoc/kr/features/persistent-connections.xml:1.2 phpdoc/kr/features/persistent-connections.xml:1.3 --- phpdoc/kr/features/persistent-connections.xml:1.2 Tue Jan 9 16:39:21 2001 +++ phpdoc/kr/features/persistent-connections.xml Tue Jan 9 21:49:22 2001 @@ -1,91 +1,76 @@ - <chapter id="features.persistent-connections"> - <title>Persistent Database Connections</title> + <chapter id="features.persistent-connections"> + <title>ì구ì ì¸ ë°ì´í°ë² ì´ì¤ ì ì (Persistent database connections)</title> <simpara> - Persistent connections are SQL links that do not close when the - execution of your script ends. When a persistent connection is - requested, PHP checks if there's already an identical persistent - connection (that remained open from earlier) - and if it exists, it - uses it. If it does not exist, it creates the link. An 'identical' - connection is a connection that was opened to the same host, with - the same username and the same password (where applicable). - </simpara> - <simpara> - People who aren't thoroughly familiar with the way web servers work - and distribute the load may mistake persistent connects for what - they're not. In particular, they do <emphasis>not</emphasis> give - you an ability to open 'user sessions' on the same SQL link, they - do <emphasis>not</emphasis> give you an ability to build up a - transaction efficently, and they don't do a whole lot of other - things. In fact, to be extremely clear about the subject, - persistent connections don't give you <emphasis>any</emphasis> - functionality that wasn't possible with their non-persistent - brothers. + ì구ì ì¸ ì ì(Persistent connection)ì ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ê° ì¢ ë£ëì´ë + SQL link를 ë«ì§ ìë ì ìì ë§íë¤. ì구ì ì¸ ì ìì´ ìì²ëë©´, + PHPë 기존ì (ì´ì ì ì´ì´ ëìë) ëì¼í(identical) ì구ì ì¸ ì ìì´ ìëê°ë¥¼ ê²ì¬íë¤. + ë§ì½ ìë¤ë©´ 기존ì ê²ì ì¬ì©íê³ , ìë¤ë©´ ìë¡ì´ link를 ë§ë ë¤. + 'ëì¼í' ì ìì´ë ê°ì í¸ì¤í¸ì ê°ì ì¬ì©ìëª ê³¼ ê°ì ìí¸ë¥¼ ì¬ì©í ì ìì ë§íë¤. </simpara> <simpara> - Why? + ê°ë ì¹ìë²ì ìëê³¼ ìì ì í ë¹ì ëí´ ì ìê³ ìì§ ëª»í ì¬ëë¤ì + ì구ì ì¸ ì ìì´ ì¬ì¤ì ë³ ê² ìëë¼ê³ ì¤í´í기ë íë¤. + í¹í, ì구ì ì¸ ì ìì´ ëì¼í SQL linkìì 'user sessions'를 ì¬ëë° ë³ ëì ê²ë ìë¤ëê°, transactionì í¨ì¨ì ì¼ë¡ ì²ë¦¬íë ê²ë ìëë¼ë¤ëê°, í¹ì ë¤ë¥¸ ì´ë¤ + í¹ë³í ê²ì íë ê²ë ìëë¼ê³ íë¤. ì¬ì¤, ì´ë° ë§ë¤ì ëí´ ëª ë°±í ë§íìë©´, + ì구ì ì¸ ì ìì ë¹ì구ì ì¸ ì ìì ë¹í´ ì´ë í 기ë¥ì ì¸ í¥ìë ì£¼ì§ ëª»íë¤. + </simpara> + <simpara> + ì? </simpara> <simpara> - This has to do with the way web servers work. There are three ways - in which your web server can utilize PHP to generate web pages. + ì´ê²ì ì¹ìë²ì ëì ë°©ìì ë°ë¼ ë¤ë¥¸ í¨ê³¼ë¥¼ ë¸ë¤. + ì¬ë¬ë¶ì ì¹ìë²ê° ì¹ íì´ì§ë¥¼ ë§ë¤ê¸°ìí´ PHP를 ì´ì©íëë°ë 3ê°ì§ ë°©ë²ì´ ìë¤. </simpara> <simpara> - The first method is to use PHP as a CGI "wrapper". When run this - way, an instance of the PHP interpreter is created and destroyed - for every page request (for a PHP page) to your web server. - Because it is destroyed after every request, any resources that it - acquires (such as a link to an SQL database server) are closed when - it is destroyed. In this case, you do not gain anything from trying - to use persistent connections -- they simply don't persist. - </simpara> - <simpara> - The second, and most popular, method is to run PHP as a module in a - multiprocess web server, which currently only includes Apache. A - multiprocess server typically has one process (the parent) which - coordinates a set of processes (its children) who actually do the - work of serving up web pages. When each request comes in from a - client, it is handed off to one of the children that is not already - serving another client. This means that when the same client makes - a second request to the server, it may be serviced by a different - child process than the first time. What a persistent connection - does for you in this case it make it so each child process only - needs to connect to your SQL server the first time that it serves a - page that makes us of such a connection. When another page then - requires a connection to the SQL server, it can reuse the - connection that child established earlier. - </simpara> - <simpara> - The last method is to use PHP as a plug-in for a multithreaded web - server. Currently this is only theoretical -- PHP does not yet work - as a plug-in for any multithreaded web servers. Work is progressing - on support for ISAPI, WSAPI, and NSAPI (on Windows), which will all - allow PHP to be used as a plug-in on multithreaded servers like - Netscape FastTrack, Microsoft's Internet Information Server (IIS), - and O'Reilly's WebSite Pro. When this happens, the behavior will be - essentially the same as for the multiprocess model described - before. - </simpara> - <simpara> - If persistent connections don't have any added functionality, what - are they good for? - </simpara> - <simpara> - The answer here is extremely simple -- efficiency. Persistent - connections are good if the overhead to create a link to your SQL - server is high. Whether or not this overhead is really high depends - on many factors. Like, what kind of database it is, whether or not - it sits on the same computer on which your web server sits, how - loaded the machine the SQL server sits on is and so forth. The - bottom line is that if that connection overhead is high, persistent - connections help you considerably. They cause the child process to - simply connect only once for its entire lifespan, instead of every - time it processes a page that requires connecting to the SQL - server. This means that for every child that opened a persistent - connection will have its own open persistent connection to the - server. For example, if you had 20 different child processes that - ran a script that made a persistent connection to your SQL server, - you'd have 20 different connections to the SQL server, one from - each child. + 첫 ë²ì§¸ ë°©ë²ì PHP를 CGI "wrapper"ì´ ííë¡ ì¬ì©íë ê²ì´ë¤. + ì´ ë°©ë²ì ê²½ì°, ì¹ìë²ì 매 PHP íì´ì§ê° ì구ë ë ë§ë¤, + PHP ì¸í°í리í°ì ì¤íì´ ë§ë¤ì´ì§ê³ ì¢ ë£ëë¤. + ë°ë¼ì 매 ìêµ¬ê° ì¢ ë£ë ëë§ë¤ ì¸í°í리í°ì ì¤íì´ ì¢ ë£ëë¯ë¡, + ì¤í ì¤ ë§ë¤ìë (SQL link를 í¬í¨í) 모ë ììì ì¤í ì¢ ë£ì ëë¶ì´ í´ì ëë¤. + ì´ ê²½ì° ì구ì ì ì ìì ì¬ì©íì¬ ì´ë¤ ì´ëë ì»ì ì ìë¤. + ë¤ë¥´ê² ë§íë©´ ì´ ê²½ì°ë ì구ì ì¸ ì ìì í´ë ì구ì ì´ ìëë¤. + </simpara> + <simpara> + ë ë²ì§¸ ë°©ë²ì ê°ì¥ ëì¤ì ì¸ ë°©ë²ì¸ë°, + PHP를 ë¤ì¤íë¡ì¸ì¤(multiprocess) ì¹ìë²ì 모ëë¡ ì¬ì©íë ê²ì´ë¤. + (íì¬ë Apacheê° ì ì¼íë¤.) ë¤ì¤íë¡ì¸ì¤ ìë²ë ë³´íµ í ê°ì ë¶ëª¨(parent) íë¡ì¸ì¤ì, + ì´ì ì 기ì ì¼ë¡ ì°ê²°ëì´ ì¹ íì´ì§ë¥¼ ì¤ì ë¡ ë§ëë ìì ì íë ì¬ë¬ê°ì + ìì(child) íë¡ì¸ì¤ë¤ì ê°ì§ê³ ìë¤. í´ë¼ì´ì¸í¸ë¡ë¶í° ë¤ì´ì¤ë ê°ë³ ì구ë + ë¤ë¥¸ í´ë¼ì´ì¸í¸ì ì구를 ì²ë¦¬íê³ ìì§ ìê³ ëê³ ìë ìì íë¡ì¸ì¤ë¡ ë겨ì§ë¤. + ì´ê²ì ëì¼í í´ë¼ì´ì¸í¸ê° ìë²ì ë ë²ì§¸ ì구를 ë³´ë¼ ë, + ë³´íµ ì²ìê³¼ ë¤ë¥¸ ìì íë¡ì¸ì¤ìì ì²ë¦¬ëë¤ë ê²ì ì미íë¤. + ì´ ê²½ì° ì구ì ì¸ ì ìì ì¬ì©íë©´ ê°ê°ì ìì íë¡ì¸ì¤ë¤ì + ìì ì´ ì²ì ì구ë°ìì ë SQL ìë²ì ì ìíê² ëë¤. + ë¤ë¥¸ íì´ì§ìì SQL ìë²ì ì ì ì구ìë ì´ì ì ë§ë¤ì´ì§ ì ìì ë¤ì ì¬ì©íê² ëë¤. + </simpara> + <simpara> + ë§ì§ë§ ë°©ë²ì PHP를 ë©í°ì°ë ë(multithreaded) ì¹ìë²ì íë¬ê·¸-ì¸ì + ííë¡ ìëìí¤ë ê²ì¸ë°, íì¬ ì´ë°©ë²ì ì´ë¡ ì ì¼ë¡ë§ ì¡´ì¬íê³ , + ì¤ì ë¡ ë§ë¤ì´ ì§ ê²ì ìë¤. ISAPI, WSAPI, NSAPI (Windowsìì) ë±ì + ë°©ë²ì ì¬ì©íì¬ Netscape FastTrack, Microsoft's Internet Information Server (IIS), + O'Reilly's WebSite Pro ë±ì ë©í°ì°ë ë ì¹ìë²ìì PHP를 íë¬ê·¸-ì¸ì¼ë¡ + ëììí¤ë ¤ë ìì ì´ íì¬ ì§íì¤ì´ë¤. ì´ ê²½ì° ê¸°ë³¸ ëìì ììì ì¸ê¸í + ë¤ì¤íë¡ì¸ì¤ 모ë¸ê³¼ ëì¼íê² ëìíë¤. + </simpara> + <simpara> + ì구ì ì¸ ì ìì´ ì¤ì ë¡ ì´ë í 기ë¥ì ì¸ í¥ìë ì£¼ì§ ëª»íë¤ë©´, + ì´ê²ì ì¬ì©í´ ì´ë¤ ì´ì ì´ ìëì? + </simpara> + <simpara> + ì´ê²ì ëí ê°ë¨í ëµì í¨ì¨ì±ì´ë¤. + ì구ì ì¸ ì ìì SQL ìë²ìì link를 ë§ëë ê²ì ë°ë¥¸ overheadê° í´ ê²½ì°ì ì ì©íë¤. + ì´ overheadë ë§ì ìì¸ì ë°ë¼ 커ì§ê¸°ë íê³ ììì§ê¸°ë íë¤. + ì´ë¤ ì¢ ë¥ì ë°ì´í°ë² ì´ì¤ì¸ê°? ì¹ìë²ì ê°ì ì»´í¨í°ì ë°ì´í°ë² ì´ì¤ ìë²ê° ìëê°? + SQL ìë²ê° ì´ë»ê² ì¬ì©ëê³ ìëê°? ë±ì ë°ë¼ í¬ê² ë¬ë¼ì§ë¤. + ì ìì ë°ë¥¸ overheadê° í´ ê²½ì°ì ì구ì ì¸ ì ìì ì¬ë¬ë¶ìê² + ì ì§ ìì ëìì ì¤ ê²ì´ë¤. ì´ê²ì ìì processìì SQL ìë²ì + ì ìì ìì²í ë ë§ë¤ ì ìì ë§ëë ëì , ì´ íë¡ì¸ì¤ê° ì¢ ë£ë ë ê¹ì§ + ì´ììë í ê°ì ì ì ë§ì ì¬ì©íë¤. ì´ê²ì 모ë ì구ì ì¸ ì ìì ì¬ì©í + íë¡ì¸ì¤ë, ê·¸ì í´ë¹íë í ëì ì구ì ì¸ ì ìì ê°ì§ê³ ìë¤ë ê²ì ì미íë¤. + ì를 ë¤ì´ SQL ìë²ì ëíì¬ ì구ì ì¸ ì ìì ì¬ì©íë ì¤í¬ë¦½í¸ë¥¼ + ì¤ííìë 20ê°ì ë¤ë¥¸ ìì íë¡ì¸ì¤ê° ìë¤ë©´, + ìë§ë ê°ê°ì ìì íë¡ì¸ì¤ìëí´ 1ê°ì©, 20ê°ì SQL ì ìì´ ìì ê²ì´ë¤. </simpara> <simpara> Note, however, that this can have some drawbacks if you are using a @@ -99,13 +84,11 @@ information on handling abandoned or idle connections. </simpara> <simpara> - An important summary. Persistent connections were designed to have - one-to-one mapping to regular connections. That means that you - should <emphasis>always</emphasis> be able to replace persistent - connections with non-persistent connections, and it won't change - the way your script behaves. It <emphasis>may</emphasis> (and - probably will) change the efficiency of the script, but not its - behavior! + ì¤ìí ì¸ê¸ íê°ì§! + ì구ì ì¸ ì ìì ì¼ë°ì ì¸ ì ìì ì¼ëì¼ë¡ ëìëëë¡ ì¤ê³ëìë¤. + ì´ê²ì ì¤í¬ë¦½í¸ì ë¤ë¥¸ ë¶ë¶ì ê·¸ëë¡ ëê³ , + ì¸ì ë¼ë ë¹ì구ì ì¸ ì°ê²°ì ì구ì ì¸ ì°ê²°ë¡ ëì¹í ì ìë¤ë ê²ì ì미íë¤. + ì´ê²ì¼ë¡ ì¬ë¬ë¶ì ìë§ë ì¤í¬ë¦½í¸ì í¨ì¨ì í¥ììí¬ ìë ìì ê²ì´ë¤. </simpara> </chapter> Index: phpdoc/kr/features/remote-files.xml diff -u phpdoc/kr/features/remote-files.xml:1.2 phpdoc/kr/features/remote-files.xml:1.3 --- phpdoc/kr/features/remote-files.xml:1.2 Tue Jan 9 16:39:21 2001 +++ phpdoc/kr/features/remote-files.xml Tue Jan 9 21:49:22 2001 @@ -1,29 +1,29 @@ - <chapter id="features.remote-files"> + <chapter id="features.remote-files"> <title>Using remote files</title> <para> - As long as support for the "URL fopen wrapper" is enabled when - you configure PHP (which it is unless you explicitly pass the - <option>--disable-url-fopen-wrapper</option> flag to configure (for versions - up to 4.0.3) or set <parameter>allow_url_fopen</parameter> to off in php.ini - (for newer versions), - you can use HTTP and FTP URLs with most functions that take a - filename as a parameter, including the <function>require</function> - and <function>include</function> statements. + ì¬ë¬ë¶ì´ PHP를 ì¤ì í ë "URL fopen wrapper"를 enableë¡ ì¤ì íìë¤ë©´ + (ì´ ì¤ì ì PHP 4.0.3 ì´íììë configure ì¤í¬ë¦½í¸ìì + <option>--disable-url-fopen-wrapper</option>ë¡ ëª ìíì§ íê±°ë, + ê·¸ ì´íì ë²ì ììë php.ini íì¼ì <parameter>allow_url_fopen</parameter>ì + offë¡ ì¤ì íì§ ìì¼ë©´ ì¤ì ëë¤.), + ì¬ë¬ë¶ì íì¼ì´ë¦ì íë¼ë©íë¡ ê°ì§ë ëë¶ë¶ì í¨ìì HTTPë FTP URLì + íì¼ì´ë¦ì¼ë¡ ì¬ì©í ì ìë¤. ì¬ì§ì´ <function>require</function>ì + <function>include</function> í¨ììë ì¬ì©ì´ ê°ë¥íë¤. </para> <para> <note> <para> - You can't use remote files in <function>include</function> and - <function>require</function> statements on Windows. + ë¨, Windowsíê²½ì <function>require</function>ì + <function>include</function> í¨ìììë ì¬ì©í ì ìë¤. </para> </note> </para> <para> - For example, you can use this to open a file on a remote web server, - parse the output for the data you want, and then use that data in a - database query, or simply to output it in a style matching the rest - of your website. + ì를 ë¤ì´, ì´ ê¸°ë¥ì ì¬ì©íì¬ ì격 ì¹ ìë²ê° ì¶ë ¥íë ë´ì©ì íì¼ë¡ ì´ê³ , + ê·¸ ì¶ë ¥ ë´ì©ìì ìíë ë°ì´í를 ë¶ìíì¬, + ì´ ìíë ë°ì´íë¡ ë°ì´íë² ì´ì¤ ì§ìì ì¬ì©íê±°ë, + ì¹ ì¬ì´í¸ì ë§ë 모ìì¼ë¡ ë³í ìì¼ ì¶ë ¥í ì ìë¤ </para> <para> <example> @@ -51,13 +51,12 @@ </example> </para> <para> - You can also write to files on an FTP as long you connect as a user - with the correct access rights, and the file doesn't exist already. - To connect as a user other than 'anonymous', you need to specify - the username (and possibly password) within the URL, such as - 'ftp://user:password@ftp.example.com/path/to/file'. (You can use the - same sort of syntax to access files via HTTP when they require Basic - authentication.) + ì¬ë¬ë¶ì í´ë¹ ìë²ì ê¶íì´ ìë ì¬ì©ìë¡ ì ìíê³ , + í´ë¹ íì¼ì´ ì¡´ì¬íì§ ìëë¤ë©´, FTP를 ì´ì©í íì¼ì ì¸ ìë ìë¤. + 'anonymous'ê° ìë ì¬ì©ìë¡ ì ìíë ¤ë©´, URLë´ì usernameì + (íìíë¤ë©´ passwordë) ë¤ìê³¼ ê°ì´ ëª ìí´ì¼ íë¤ : + 'ftp://user:password@ftp.example.com/path/to/file'. + (ëí HTTPìì Basic authenticationì ì¬ì©í ì¸ì¦ì ì구íë ê²½ì°ìë ì´ì ê°ì 문ë²ì ì¬ì©í ì ìë¤.) </para> <para> <example> @@ -81,11 +80,9 @@ <para> <note> <para> - You might get the idea from the example above to use this - technique to write to a remote log, but as mentioned above, you - can only write to a new file using the URL fopen() wrappers. To - do distributed logging like that, you should take a look at - <function>syslog</function>. + ì¬ë¬ë¶ì ìì ìì 를 ë³´ê³ , ì´ í í¬ëì ì¬ì©íì¬ remote log를 ìì±í ì ìê² ë¤ê³ ìê°í ìë ìë¤. + ê·¸ë¬ë ìì ì¸ê¸íëë¡ URL fopen() wrapperë ì íì¼ìë§ ì¸ ì ìë¤. + ì¬ë¬ë¶ì´ ìíë ëë¡ ë¶ì°ë log를 íê³ ì¶ë¤ë©´ <function>syslog</function>ì ë´ì©ì ì´í´ë³´ë¼. </para> </note> </para>
Index: phpdoc/kr/features/connection-handling.xml diff -u phpdoc/kr/features/connection-handling.xml:1.2 phpdoc/kr/features/connection-handling.xml:1.3 --- phpdoc/kr/features/connection-handling.xml:1.2 Tue Jan 9 16:39:21 2001 +++ phpdoc/kr/features/connection-handling.xml Tue Jan 9 21:49:22 2001 @@ -1,13 +1,12 @@ - <chapter id="features.connection-handling"> + <chapter id="features.connection-handling"> <title>Connection handling</title> <note> - <para>The following applies to 3.0.7 and later.</para> + <para>ì´ ê¸°ë¥ì PHP version 3.0.7 ì´íë¶í° ì ì©ë ê²ë¤ì´ë¤.</para> </note> <para> - Internally in PHP a connection status is maintained. There are 3 - possible states: + ë´ë¶ì ì¼ë¡ PHPë ì°ê²°ì ìí를 ë¤ì 3ê°ì§ì¤ íëë¡ ì¤ì íë¤. : <itemizedlist> <listitem><simpara>0 - NORMAL</simpara></listitem> <listitem><simpara>1 - ABORTED</simpara></listitem> @@ -16,60 +15,55 @@ </para> <simpara> - When a PHP script is running normally the NORMAL state, is active. - If the remote client disconnects the ABORTED state flag is - turned on. A remote client disconnect is usually caused by the - user hitting his STOP button. If the PHP-imposed time limit (see - <function>set_time_limit</function>) is hit, the TIMEOUT state flag - is turned on.</simpara> + PHP ì¤í¬ë¦½í¸ê° ì¼ë°ì ì¼ë¡ ì¤íëê³ ìì ëë NORMAL ìíê° activeëë¤. + ë§ì½ ì격 í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëê²ëë©´ ABORTED ìí flagê° ì¼ì§ê² ëë¤. + ë³´íµ í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëë ê²ì ì¬ì©ìê° STOP ë²í¼ì ëë ì ë ì¼ì´ëë¤. + ë§ì½ PHPê° ì¤ì í ìê° ì íì (<function>set_time_limit</function>ì ë³´ë¼) ê±¸ë¦¬ê² ëë©´ + TIMEOUT ìí flagê° ì¼ì§ê² ëë¤. + </simpara> <simpara> - You can decide whether or not you want a client disconnect to cause - your script to be aborted. Sometimes it is handy to always have your - scripts run to completion even if there is no remote browser receiving - the output. The default behaviour is however for your script to be - aborted when the remote client disconnects. This behaviour can be - set via the ignore_user_abort php3.ini directive as well as through - the corresponding php3_ignore_user_abort Apache .conf directive or - with the <function>ignore_user_abort</function> function. If you do - not tell PHP to ignore a user abort and the user aborts, your script - will terminate. The one exception is if you have registered a shutdown - function using <function>register_shutdown_function</function>. With a - shutdown function, when the remote user hits his STOP button, the - next time your script tries to output something PHP will detect that - the connection has been aborted and the shutdown function is called. - This shutdown function will also get called at the end of your script - terminating normally, so to do something different in case of a client - diconnect you can use the <function>connection_aborted</function> - function. This function will return true if the connection was - aborted.</simpara> + ì¬ë¬ë¶ì í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëìì ë ì¤í¬ë¦½í¸ê° ìíì ì¤ë¨í ê²ì¸ê° ìëê°ë¥¼ ê²°ì íì¬ì¼ íë¤. + ëëë¡ ì격 ë¸ë¼ì°ì ê° ì´ë¤ ê²°ê³¼ë ë°ìë¤ì´ì§ ìëë¼ë ì¤í¬ë¦½í¸ë¥¼ ëê¹ì§ ì¤ííë ê²ì´ í¸ë¦¬í ëê° ë§ë¤. + 기본 ëìì í´ë¼ì´ì¸í¸ê° ì°ê²°ì ëì¼ë©´ ì¤í¬ë¦½í¸ë ì¤ë¨ëë ê²ì´ë¤. + ì´ ëìì ignore_user_abortë¼ë php3.ini ì§ìì(directive)ë, + php3_ignore_user_abortë¼ë Apacheì .confì ì§ììë¡ ì¤ì ì´ ê°ë¥íê³ , + <function>ignore_user_abort</function> í¨ì를 ì¬ì©íì¬ ì¤ì í ìë ìë¤. + ë§ì½ PHPìê² ì¬ì©ìê° ë´ë¦° ì¤ì§ ëª ë ¹ì 무ìíë¼ê³ ë§í´ì£¼ì§ ììë¤ë©´, + ì¬ì©ìì ì¤ì§ ì í¸ë ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ë¥¼ ì¢ ë£ìí¨ë¤. + ë¨, <function>register_shutdown_function</function>ì ì¬ì©íì¬ + shutdown í¨ì를 ë±ë¡í´ ëì ê²½ì°ë ìì¸ê° ëë¤. + shutdown í¨ì를 ì¬ì©íë©´, ì¬ì©ìê° STOPë²í¼ì ëë ì ë, + ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ë ë¨ì ì¶ë ¥ì íë ¤ê³ íê³ , + PHPë ì°ê²°ì´ ì¤ë¨ëììì ì¸ì§íì¬ shutdown í¨ì를 í¸ì¶íê² ëë¤. + shutdown í¨ìë ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ê° ì ìì ì¼ë¡ ì¢ ë£ëìì ëë í¸ì¶ ëë¤. + ë§ì½ ì¬ê¸°ì í´ë¼ì´ì¸í¸ì ì°ê²° ì¤ë¨ ëì ì¼ë°ì ì¸ ì¢ ë£ìì ë¤ë¥¸ ëìì ìíë¤ë©´ + <function>connection_aborted</function> í¨ì를 ì¬ì©íë©´ ëë¤. + ì´ í¨ìë ì°ê²°ì´ ì¤ë¨ëìë¤ë©´ true를 ë°ííë¤. + </simpara> <simpara> - Your script can also be terminated by the built-in script timer. - The default timeout is 30 seconds. It can be changed using - the max_execution_time php3.ini directive or the corresponding - php3_max_execution_time Apache .conf directive as well as with - the <function>set_time_limit</function> function. When the timer - expires the script will be aborted and as with the above client - disconnect case, if a shutdown function has been registered it will - be called. Within this shutdown function you can check to see if - a timeout caused the shutdown function to be called by calling the - <function>connection_timeout</function> function. This function will - return true if a timeout caused the shutdown function to be called.</simpara> - + ì¤í¬ë¦½í¸ë ë´ì¥ë íì´ë¨¸ì ìí´ ì¢ ë£ë ì ìë¤. + 기본 timeout ìê°ì 30ì´ë¡ ëì´ ìë¤. + ì´ê²ì max_execution_timeì´ë¼ë php3.ini ì§ìì(directive)ë, + ëì¼í ë´ì©ì php3_max_execution_timeì´ë¼ë Apacheì .conf ì§ììì ìí´ + ë¤ë¥´ê² ì¤ì ì´ ê°ë¥íê³ <function>set_time_limit</function> í¨ì를 ì¬ì©íì¬ ì¤ì í ìë ìë¤. + ì¤ì í ìê°ì´ 경과íë©´ ì¤í¬ë¦½í¸ë ìëì¼ë¡ ì¤ë¨ëê³ , + ì´ ì¤í¬ë¦½í¸ë ìì ì¤ëª í í´ë¼ì´ì¸í¸ìì ì°ê²°ì´ ì¢ ë£ë ê²ì²ë¼ ëìíë¤. + ë°ë¼ì shutdown í¨ìê° ë±ë¡ëì´ ìë¤ë©´ ì´ í¨ìê° ì¤íëë¤. + shutdown í¨ìë´ìì ì´ í¨ìê° timeoutì ìí´ í¸ì¶ë ê²ì¸ê°ë¥¼ íë¨íë ¤ë©´ + <function>connection_timeout</function> í¨ì를 ì¬ì©íë©´ ëë¤. + ì´ í¨ìë timeoutì ìí´ shutdown í¨ìê° í¸ì¶ëìë¤ë©´ true를 ë°ííë¤. + </simpara> <simpara> - One thing to note is that both the ABORTED and the TIMEOUT states - can be active at the same time. This is possible if you tell - PHP to ignore user aborts. PHP will still note the fact that - a user may have broken the connection, but the script will keep - running. If it then hits the time limit it will be aborted and - your shutdown function, if any, will be called. At this point - you will find that <function>connection_timeout</function> - and <function>connection_aborted</function> return true. - You can also check both states in a single call by using the - <function>connection_status</function>. This function returns a - bitfield of the active states. So, if both states are active it - would return 3, for example.</simpara> + íê°ì§ ì ìí ì¬íì ABORTEDì TIMEOUT ìíë ë ê°ê° ëìì activeë ì ìë¤ë ê²ì´ë¤. + ì´ê²ì PHPê° ì¬ì©ì ì¤ë¨ì 무ìíëë¡ ì¤ì í´ ëìì ë ì길 ì ìë¤. + ë ë¤ë¥¸ ê²½ì°ë ì¬ì©ìê° ì°ê²°ì ëì§ë ììì§ë§ ì°ê²°ì ì´ë¤ 문ì ê° ì겨 ì°ê²°ì´ ë§ê°ì§ ê²½ì°ë¡, + ì´ë° ê²½ì°ì ì¤í¬ë¦½í¸ë ê³ìì¤íëê³ , ìê° ì íì ê±¸ë ¤ ì¤í¬ë¦½í¸ì ìíì´ ì¤ë¨ëê³ shutdown í¨ìê° í¸ì¶ëë©´, <function>connection_timeout</function>ê³¼ <function>connection_aborted</function>í¨ì 모ë true를 ë°ííê² ëë¤. + ì¬ë¬ë¶ì <function>connection_status</function> í¨ì를 ì¬ì©íì¬ ëê°ì§ ìí 모ë를 ê²ì¬í ì ìë¤. + í¨ìë ê° ìíì ëí ì 보를 bitë¨ìë¡ ê°ì§ê³ ìë¤. + 를ë¤ì´ ììê°ì´ ABORTì TIMEOUT ë ê°ì ìíê° ëª¨ë activeëì´ ìë¤ë©´ ì´ í¨ìë 3ì ë°ííë¤. + </simpara> </chapter> Index: phpdoc/kr/features/persistent-connections.xml diff -u phpdoc/kr/features/persistent-connections.xml:1.2 phpdoc/kr/features/persistent-connections.xml:1.3 --- phpdoc/kr/features/persistent-connections.xml:1.2 Tue Jan 9 16:39:21 2001 +++ phpdoc/kr/features/persistent-connections.xml Tue Jan 9 21:49:22 2001 @@ -1,91 +1,76 @@ - <chapter id="features.persistent-connections"> - <title>Persistent Database Connections</title> + <chapter id="features.persistent-connections"> + <title>ì구ì ì¸ ë°ì´í°ë² ì´ì¤ ì ì (Persistent database connections)</title> <simpara> - Persistent connections are SQL links that do not close when the - execution of your script ends. When a persistent connection is - requested, PHP checks if there's already an identical persistent - connection (that remained open from earlier) - and if it exists, it - uses it. If it does not exist, it creates the link. An 'identical' - connection is a connection that was opened to the same host, with - the same username and the same password (where applicable). - </simpara> - <simpara> - People who aren't thoroughly familiar with the way web servers work - and distribute the load may mistake persistent connects for what - they're not. In particular, they do <emphasis>not</emphasis> give - you an ability to open 'user sessions' on the same SQL link, they - do <emphasis>not</emphasis> give you an ability to build up a - transaction efficently, and they don't do a whole lot of other - things. In fact, to be extremely clear about the subject, - persistent connections don't give you <emphasis>any</emphasis> - functionality that wasn't possible with their non-persistent - brothers. + ì구ì ì¸ ì ì(Persistent connection)ì ì¬ë¬ë¶ì ì¤í¬ë¦½í¸ê° ì¢ ë£ëì´ë + SQL link를 ë«ì§ ìë ì ìì ë§íë¤. ì구ì ì¸ ì ìì´ ìì²ëë©´, + PHPë 기존ì (ì´ì ì ì´ì´ ëìë) ëì¼í(identical) ì구ì ì¸ ì ìì´ ìëê°ë¥¼ ê²ì¬íë¤. + ë§ì½ ìë¤ë©´ 기존ì ê²ì ì¬ì©íê³ , ìë¤ë©´ ìë¡ì´ link를 ë§ë ë¤. + 'ëì¼í' ì ìì´ë ê°ì í¸ì¤í¸ì ê°ì ì¬ì©ìëª ê³¼ ê°ì ìí¸ë¥¼ ì¬ì©í ì ìì ë§íë¤. </simpara> <simpara> - Why? + ê°ë ì¹ìë²ì ìëê³¼ ìì ì í ë¹ì ëí´ ì ìê³ ìì§ ëª»í ì¬ëë¤ì + ì구ì ì¸ ì ìì´ ì¬ì¤ì ë³ ê² ìëë¼ê³ ì¤í´í기ë íë¤. + í¹í, ì구ì ì¸ ì ìì´ ëì¼í SQL linkìì 'user sessions'를 ì¬ëë° ë³ ëì ê²ë ìë¤ëê°, transactionì í¨ì¨ì ì¼ë¡ ì²ë¦¬íë ê²ë ìëë¼ë¤ëê°, í¹ì ë¤ë¥¸ ì´ë¤ + í¹ë³í ê²ì íë ê²ë ìëë¼ê³ íë¤. ì¬ì¤, ì´ë° ë§ë¤ì ëí´ ëª ë°±í ë§íìë©´, + ì구ì ì¸ ì ìì ë¹ì구ì ì¸ ì ìì ë¹í´ ì´ë í 기ë¥ì ì¸ í¥ìë ì£¼ì§ ëª»íë¤. + </simpara> + <simpara> + ì? </simpara> <simpara> - This has to do with the way web servers work. There are three ways - in which your web server can utilize PHP to generate web pages. + ì´ê²ì ì¹ìë²ì ëì ë°©ìì ë°ë¼ ë¤ë¥¸ í¨ê³¼ë¥¼ ë¸ë¤. + ì¬ë¬ë¶ì ì¹ìë²ê° ì¹ íì´ì§ë¥¼ ë§ë¤ê¸°ìí´ PHP를 ì´ì©íëë°ë 3ê°ì§ ë°©ë²ì´ ìë¤. </simpara> <simpara> - The first method is to use PHP as a CGI "wrapper". When run this - way, an instance of the PHP interpreter is created and destroyed - for every page request (for a PHP page) to your web server. - Because it is destroyed after every request, any resources that it - acquires (such as a link to an SQL database server) are closed when - it is destroyed. In this case, you do not gain anything from trying - to use persistent connections -- they simply don't persist. - </simpara> - <simpara> - The second, and most popular, method is to run PHP as a module in a - multiprocess web server, which currently only includes Apache. A - multiprocess server typically has one process (the parent) which - coordinates a set of processes (its children) who actually do the - work of serving up web pages. When each request comes in from a - client, it is handed off to one of the children that is not already - serving another client. This means that when the same client makes - a second request to the server, it may be serviced by a different - child process than the first time. What a persistent connection - does for you in this case it make it so each child process only - needs to connect to your SQL server the first time that it serves a - page that makes us of such a connection. When another page then - requires a connection to the SQL server, it can reuse the - connection that child established earlier. - </simpara> - <simpara> - The last method is to use PHP as a plug-in for a multithreaded web - server. Currently this is only theoretical -- PHP does not yet work - as a plug-in for any multithreaded web servers. Work is progressing - on support for ISAPI, WSAPI, and NSAPI (on Windows), which will all - allow PHP to be used as a plug-in on multithreaded servers like - Netscape FastTrack, Microsoft's Internet Information Server (IIS), - and O'Reilly's WebSite Pro. When this happens, the behavior will be - essentially the same as for the multiprocess model described - before. - </simpara> - <simpara> - If persistent connections don't have any added functionality, what - are they good for? - </simpara> - <simpara> - The answer here is extremely simple -- efficiency. Persistent - connections are good if the overhead to create a link to your SQL - server is high. Whether or not this overhead is really high depends - on many factors. Like, what kind of database it is, whether or not - it sits on the same computer on which your web server sits, how - loaded the machine the SQL server sits on is and so forth. The - bottom line is that if that connection overhead is high, persistent - connections help you considerably. They cause the child process to - simply connect only once for its entire lifespan, instead of every - time it processes a page that requires connecting to the SQL - server. This means that for every child that opened a persistent - connection will have its own open persistent connection to the - server. For example, if you had 20 different child processes that - ran a script that made a persistent connection to your SQL server, - you'd have 20 different connections to the SQL server, one from - each child. + 첫 ë²ì§¸ ë°©ë²ì PHP를 CGI "wrapper"ì´ ííë¡ ì¬ì©íë ê²ì´ë¤. + ì´ ë°©ë²ì ê²½ì°, ì¹ìë²ì 매 PHP íì´ì§ê° ì구ë ë ë§ë¤, + PHP ì¸í°í리í°ì ì¤íì´ ë§ë¤ì´ì§ê³ ì¢ ë£ëë¤. + ë°ë¼ì 매 ìêµ¬ê° ì¢ ë£ë ëë§ë¤ ì¸í°í리í°ì ì¤íì´ ì¢ ë£ëë¯ë¡, + ì¤í ì¤ ë§ë¤ìë (SQL link를 í¬í¨í) 모ë ììì ì¤í ì¢ ë£ì ëë¶ì´ í´ì ëë¤. + ì´ ê²½ì° ì구ì ì ì ìì ì¬ì©íì¬ ì´ë¤ ì´ëë ì»ì ì ìë¤. + ë¤ë¥´ê² ë§íë©´ ì´ ê²½ì°ë ì구ì ì¸ ì ìì í´ë ì구ì ì´ ìëë¤. + </simpara> + <simpara> + ë ë²ì§¸ ë°©ë²ì ê°ì¥ ëì¤ì ì¸ ë°©ë²ì¸ë°, + PHP를 ë¤ì¤íë¡ì¸ì¤(multiprocess) ì¹ìë²ì 모ëë¡ ì¬ì©íë ê²ì´ë¤. + (íì¬ë Apacheê° ì ì¼íë¤.) ë¤ì¤íë¡ì¸ì¤ ìë²ë ë³´íµ í ê°ì ë¶ëª¨(parent) íë¡ì¸ì¤ì, + ì´ì ì 기ì ì¼ë¡ ì°ê²°ëì´ ì¹ íì´ì§ë¥¼ ì¤ì ë¡ ë§ëë ìì ì íë ì¬ë¬ê°ì + ìì(child) íë¡ì¸ì¤ë¤ì ê°ì§ê³ ìë¤. í´ë¼ì´ì¸í¸ë¡ë¶í° ë¤ì´ì¤ë ê°ë³ ì구ë + ë¤ë¥¸ í´ë¼ì´ì¸í¸ì ì구를 ì²ë¦¬íê³ ìì§ ìê³ ëê³ ìë ìì íë¡ì¸ì¤ë¡ ë겨ì§ë¤. + ì´ê²ì ëì¼í í´ë¼ì´ì¸í¸ê° ìë²ì ë ë²ì§¸ ì구를 ë³´ë¼ ë, + ë³´íµ ì²ìê³¼ ë¤ë¥¸ ìì íë¡ì¸ì¤ìì ì²ë¦¬ëë¤ë ê²ì ì미íë¤. + ì´ ê²½ì° ì구ì ì¸ ì ìì ì¬ì©íë©´ ê°ê°ì ìì íë¡ì¸ì¤ë¤ì + ìì ì´ ì²ì ì구ë°ìì ë SQL ìë²ì ì ìíê² ëë¤. + ë¤ë¥¸ íì´ì§ìì SQL ìë²ì ì ì ì구ìë ì´ì ì ë§ë¤ì´ì§ ì ìì ë¤ì ì¬ì©íê² ëë¤. + </simpara> + <simpara> + ë§ì§ë§ ë°©ë²ì PHP를 ë©í°ì°ë ë(multithreaded) ì¹ìë²ì íë¬ê·¸-ì¸ì + ííë¡ ìëìí¤ë ê²ì¸ë°, íì¬ ì´ë°©ë²ì ì´ë¡ ì ì¼ë¡ë§ ì¡´ì¬íê³ , + ì¤ì ë¡ ë§ë¤ì´ ì§ ê²ì ìë¤. ISAPI, WSAPI, NSAPI (Windowsìì) ë±ì + ë°©ë²ì ì¬ì©íì¬ Netscape FastTrack, Microsoft's Internet Information Server (IIS), + O'Reilly's WebSite Pro ë±ì ë©í°ì°ë ë ì¹ìë²ìì PHP를 íë¬ê·¸-ì¸ì¼ë¡ + ëììí¤ë ¤ë ìì ì´ íì¬ ì§íì¤ì´ë¤. ì´ ê²½ì° ê¸°ë³¸ ëìì ììì ì¸ê¸í + ë¤ì¤íë¡ì¸ì¤ 모ë¸ê³¼ ëì¼íê² ëìíë¤. + </simpara> + <simpara> + ì구ì ì¸ ì ìì´ ì¤ì ë¡ ì´ë í 기ë¥ì ì¸ í¥ìë ì£¼ì§ ëª»íë¤ë©´, + ì´ê²ì ì¬ì©í´ ì´ë¤ ì´ì ì´ ìëì? + </simpara> + <simpara> + ì´ê²ì ëí ê°ë¨í ëµì í¨ì¨ì±ì´ë¤. + ì구ì ì¸ ì ìì SQL ìë²ìì link를 ë§ëë ê²ì ë°ë¥¸ overheadê° í´ ê²½ì°ì ì ì©íë¤. + ì´ overheadë ë§ì ìì¸ì ë°ë¼ 커ì§ê¸°ë íê³ ììì§ê¸°ë íë¤. + ì´ë¤ ì¢ ë¥ì ë°ì´í°ë² ì´ì¤ì¸ê°? ì¹ìë²ì ê°ì ì»´í¨í°ì ë°ì´í°ë² ì´ì¤ ìë²ê° ìëê°? + SQL ìë²ê° ì´ë»ê² ì¬ì©ëê³ ìëê°? ë±ì ë°ë¼ í¬ê² ë¬ë¼ì§ë¤. + ì ìì ë°ë¥¸ overheadê° í´ ê²½ì°ì ì구ì ì¸ ì ìì ì¬ë¬ë¶ìê² + ì ì§ ìì ëìì ì¤ ê²ì´ë¤. ì´ê²ì ìì processìì SQL ìë²ì + ì ìì ìì²í ë ë§ë¤ ì ìì ë§ëë ëì , ì´ íë¡ì¸ì¤ê° ì¢ ë£ë ë ê¹ì§ + ì´ììë í ê°ì ì ì ë§ì ì¬ì©íë¤. ì´ê²ì 모ë ì구ì ì¸ ì ìì ì¬ì©í + íë¡ì¸ì¤ë, ê·¸ì í´ë¹íë í ëì ì구ì ì¸ ì ìì ê°ì§ê³ ìë¤ë ê²ì ì미íë¤. + ì를 ë¤ì´ SQL ìë²ì ëíì¬ ì구ì ì¸ ì ìì ì¬ì©íë ì¤í¬ë¦½í¸ë¥¼ + ì¤ííìë 20ê°ì ë¤ë¥¸ ìì íë¡ì¸ì¤ê° ìë¤ë©´, + ìë§ë ê°ê°ì ìì íë¡ì¸ì¤ìëí´ 1ê°ì©, 20ê°ì SQL ì ìì´ ìì ê²ì´ë¤. </simpara> <simpara> Note, however, that this can have some drawbacks if you are using a @@ -99,13 +84,11 @@ information on handling abandoned or idle connections. </simpara> <simpara> - An important summary. Persistent connections were designed to have - one-to-one mapping to regular connections. That means that you - should <emphasis>always</emphasis> be able to replace persistent - connections with non-persistent connections, and it won't change - the way your script behaves. It <emphasis>may</emphasis> (and - probably will) change the efficiency of the script, but not its - behavior! + ì¤ìí ì¸ê¸ íê°ì§! + ì구ì ì¸ ì ìì ì¼ë°ì ì¸ ì ìì ì¼ëì¼ë¡ ëìëëë¡ ì¤ê³ëìë¤. + ì´ê²ì ì¤í¬ë¦½í¸ì ë¤ë¥¸ ë¶ë¶ì ê·¸ëë¡ ëê³ , + ì¸ì ë¼ë ë¹ì구ì ì¸ ì°ê²°ì ì구ì ì¸ ì°ê²°ë¡ ëì¹í ì ìë¤ë ê²ì ì미íë¤. + ì´ê²ì¼ë¡ ì¬ë¬ë¶ì ìë§ë ì¤í¬ë¦½í¸ì í¨ì¨ì í¥ììí¬ ìë ìì ê²ì´ë¤. </simpara> </chapter> Index: phpdoc/kr/features/remote-files.xml diff -u phpdoc/kr/features/remote-files.xml:1.2 phpdoc/kr/features/remote-files.xml:1.3 --- phpdoc/kr/features/remote-files.xml:1.2 Tue Jan 9 16:39:21 2001 +++ phpdoc/kr/features/remote-files.xml Tue Jan 9 21:49:22 2001 @@ -1,29 +1,29 @@ - <chapter id="features.remote-files"> + <chapter id="features.remote-files"> <title>Using remote files</title> <para> - As long as support for the "URL fopen wrapper" is enabled when - you configure PHP (which it is unless you explicitly pass the - <option>--disable-url-fopen-wrapper</option> flag to configure (for versions - up to 4.0.3) or set <parameter>allow_url_fopen</parameter> to off in php.ini - (for newer versions), - you can use HTTP and FTP URLs with most functions that take a - filename as a parameter, including the <function>require</function> - and <function>include</function> statements. + ì¬ë¬ë¶ì´ PHP를 ì¤ì í ë "URL fopen wrapper"를 enableë¡ ì¤ì íìë¤ë©´ + (ì´ ì¤ì ì PHP 4.0.3 ì´íììë configure ì¤í¬ë¦½í¸ìì + <option>--disable-url-fopen-wrapper</option>ë¡ ëª ìíì§ íê±°ë, + ê·¸ ì´íì ë²ì ììë php.ini íì¼ì <parameter>allow_url_fopen</parameter>ì + offë¡ ì¤ì íì§ ìì¼ë©´ ì¤ì ëë¤.), + ì¬ë¬ë¶ì íì¼ì´ë¦ì íë¼ë©íë¡ ê°ì§ë ëë¶ë¶ì í¨ìì HTTPë FTP URLì + íì¼ì´ë¦ì¼ë¡ ì¬ì©í ì ìë¤. ì¬ì§ì´ <function>require</function>ì + <function>include</function> í¨ììë ì¬ì©ì´ ê°ë¥íë¤. </para> <para> <note> <para> - You can't use remote files in <function>include</function> and - <function>require</function> statements on Windows. + ë¨, Windowsíê²½ì <function>require</function>ì + <function>include</function> í¨ìììë ì¬ì©í ì ìë¤. </para> </note> </para> <para> - For example, you can use this to open a file on a remote web server, - parse the output for the data you want, and then use that data in a - database query, or simply to output it in a style matching the rest - of your website. + ì를 ë¤ì´, ì´ ê¸°ë¥ì ì¬ì©íì¬ ì격 ì¹ ìë²ê° ì¶ë ¥íë ë´ì©ì íì¼ë¡ ì´ê³ , + ê·¸ ì¶ë ¥ ë´ì©ìì ìíë ë°ì´í를 ë¶ìíì¬, + ì´ ìíë ë°ì´íë¡ ë°ì´íë² ì´ì¤ ì§ìì ì¬ì©íê±°ë, + ì¹ ì¬ì´í¸ì ë§ë 모ìì¼ë¡ ë³í ìì¼ ì¶ë ¥í ì ìë¤ </para> <para> <example> @@ -51,13 +51,12 @@ </example> </para> <para> - You can also write to files on an FTP as long you connect as a user - with the correct access rights, and the file doesn't exist already. - To connect as a user other than 'anonymous', you need to specify - the username (and possibly password) within the URL, such as - 'ftp://user:password@ftp.example.com/path/to/file'. (You can use the - same sort of syntax to access files via HTTP when they require Basic - authentication.) + ì¬ë¬ë¶ì í´ë¹ ìë²ì ê¶íì´ ìë ì¬ì©ìë¡ ì ìíê³ , + í´ë¹ íì¼ì´ ì¡´ì¬íì§ ìëë¤ë©´, FTP를 ì´ì©í íì¼ì ì¸ ìë ìë¤. + 'anonymous'ê° ìë ì¬ì©ìë¡ ì ìíë ¤ë©´, URLë´ì usernameì + (íìíë¤ë©´ passwordë) ë¤ìê³¼ ê°ì´ ëª ìí´ì¼ íë¤ : + 'ftp://user:password@ftp.example.com/path/to/file'. + (ëí HTTPìì Basic authenticationì ì¬ì©í ì¸ì¦ì ì구íë ê²½ì°ìë ì´ì ê°ì 문ë²ì ì¬ì©í ì ìë¤.) </para> <para> <example> @@ -81,11 +80,9 @@ <para> <note> <para> - You might get the idea from the example above to use this - technique to write to a remote log, but as mentioned above, you - can only write to a new file using the URL fopen() wrappers. To - do distributed logging like that, you should take a look at - <function>syslog</function>. + ì¬ë¬ë¶ì ìì ìì 를 ë³´ê³ , ì´ í í¬ëì ì¬ì©íì¬ remote log를 ìì±í ì ìê² ë¤ê³ ìê°í ìë ìë¤. + ê·¸ë¬ë ìì ì¸ê¸íëë¡ URL fopen() wrapperë ì íì¼ìë§ ì¸ ì ìë¤. + ì¬ë¬ë¶ì´ ìíë ëë¡ ë¶ì°ë log를 íê³ ì¶ë¤ë©´ <function>syslog</function>ì ë´ì©ì ì´í´ë³´ë¼. </para> </note> </para>