Design - PHPファイルを統合しますか？

Question

私の理解は、「名前」.class.phpはPHPでクラスを作成するための標準規則であり、その結果、クラスごとに別のファイルがあります。私がやりたいことは、私の小さなPHPクラスの階層を1つの単一のファイルに統合することです... consoleidated.class.phpと言う。

これは、サーバーにアップロード/ダウンロードすることが簡単になります+簡単なテキスト検索を実行する必要がある場合は、1つのファイルを探す必要がありません。さらに、私は基本的にそれらを挿入するので、私は包含/要求を削除することができます。

問題は、パフォーマンスのヒットを受けて統合できますか？

編集/更新

多くの時間後、私は別々のファイルとオートローダを使っています。これはより効率的になるはずですが、もちろん、ファイルのサイズに依存しています。

Answer 1

The reason people use the one class per file convention is for class autoloaders. This allows your script to automatically only load code that is actually being used by your script in that particular instance. If you load ALL of you classes every time a page loads, it's a fairly inneficient way to go.

For more information about class autoloaders:

http://php.net/manual/en/language.oop5.autoload.php

http://php.net/manual/en/function.spl-autoload-register.php

Answer 2

I believe it depends on the size of the project. You can start small, with everything in just a single file, then, as the code accumulates and you get a better understanding of the domain you're modelling, you can extract units into separate files.

The convention to use a class per file comes from the Java world. For years, PHP has tried to imitate Java, however, some of the practices are absurd. Like, you can't have functions, just classes, even if they're nothing more than a collection of static methods.

Here's an example of a web framework, called Konstrukt, that uses multiple units (classes/functions/constants) per file and seems to be doing well.

As @Nabeel said, you may hit a point where you'd have problems locating code if everything is inside a single big file. Judge by the project you're developing.

Regarding performance, you'd have to benchmark, as once again it depends on the project, but require/include incur some performance overhead due to file I/O. So it might be better that you have a single file loaded per request. The actual parsing might be faster than the system calls that look for the file to require.

Answer 3

I would advise you not to do this because everything a page gets viewed, every single one of your classes is loaded. When using only a few classes which are loaded everytime, it does indeed make no difference performance-wise, but if you have quite a lot of classes and you only use a handful, depending on the page being loaded, you add a huge overload to the page.

Answer 4

I don't want to say the same things like others (which is actually correct ^^) to bring u some new ideas.

I would create few functions to include/require my class files.

Example:

you have 2 php-files:

1: login.php

2: register.php

<?php
   // login.php
   include '../system/functions/myFunctions.php';  
   loadMyClasses(1);
?>

<?php
  // register.php
  include '../system/functions/myFunctions.php';
  loadMyClasses(2); 
?>

<?php
  //myFunctions.php

  DEFINE("CLASS_PATH", "../system/class/");      

  function loadMyClasses($type_id)
  {  
     //Example: Load in everytime. These files are always required.
     require_once CLASS_PATH.'class.database.php';
     require_once CLASS_PATH.'class.sql.php';

     if($type_id == 1)
     {
           require(CLASS_PATH.'class.security.php');
           require(CLASS_PATH.'class.cryptor.php');   
           require(CLASS_PATH.'class.login.php');   
     }

     if($type_id == 2)
     {
           require(CLASS_PATH.'class.security.php'); 
           require(CLASS_PATH.'class.register.php');  
     }
  }
?>

And this way you can simply change the path of the class or interface files. You have to make changes only in one file.

I Hope, I was able to help a bit!