검색어: production (한국어 - 일본어)

for security reasons, you should not put your dynamic modules into publicly accessible directories. even though it can be done and it simplifies testing, you should put them into a separate directory in production environments.
for security reasons, you should not put your dynamic modules into publicly accessible directories. even though it can be done and it simplifies testing, you should put them into a separate directory in production environments.

php 4.0 and the integrated zend engine have greatly inproved phps performance and capabilities, but great care has been taken to break as little existing code as possible. so migrating your code from php 3.0 to 4.0 should be much easier than migrating from php/fi 2.0 to php 3.0. a lot of existing php 3.0 code should be ready to run without changes, but you should still know about the few differences and take care to test your code before switching versions in production environments. the following should give you some hints about what to look for.
php 4とこれに組み込まれたzendエンジンは、phpの性能と機能を大 幅に向上させますが、既存のコードへの変更は最小限ですむように多くの 考慮がなされています。このため、php 3から4への移行は、 php/fi 2.0から php 3への移行と比べて非常に容易です。既存の php 3のコードの多くは無修正で実行可能です。しかし、実用環境でバージョ ンを切替える際には、バージョン間の若干の差異を知り、使用するコード について確認を行うことが必要です。以下の記述は、これらの事項につい ていくつかの示唆を与えるものです。