Jump to content

trq

Staff Alumni
  • Content Count

    30,999
  • Joined

  • Last visited

  • Days Won

    26

trq last won the day on September 10 2014

trq had the most liked content!

Community Reputation

255 Excellent

About trq

  • Rank
    Prolific Member
  • Birthday 06/12/1975

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The simplest way to gain request-start to request-end speed is to cache using something like akamai.
  2. Composer ships with an autoloader, just stick to one of the standards and use that.
  3. The point I'm trying to make is why have the rewrite at all if you're just going to use normal querystring parameters? I understand you want to force everything through a front controller, but why stop there? But yeah, you could just use the QSA flag to have apache append existing parameters. RewriteRule ^(.*)$ index.php?uri=$1 [PT,L,QSA]
  4. That rewrite rule removes the need for typical GET parameters by making your urls "pretty". So instead of this: users/activate-account?email_address=test&token=test You would use something more like: users/activate-account/test/test Of course then you need some sort of "router" to parse and handle these parameters for you. If this is your own framework you need to decide how your urls are going to be formed.
  5. Why? The only reason to do this is laziness. It is making your code tightly coupled to whatever this "god" object is. A controller has no interest in your connection settings for instance. Objects should be passed their dependencies (and only their dependencies) at construction time. Most frameworks handle this in an easy to manage manor by providing a configurable dependency injection container which allows you to configure how objects are to be created.
  6. You don't need a regex unless you actually need to match a pattern.. <?php if (substr_count($path, '/') > 2) { echo "Directories too deep"; }
  7. Why would you edit the index.php file? PHP is a programming language, you can use it to dynamically display data from different data sources. Having cron dynamically alter the PHP "script" is ridiculous. Instead, have your cron job put the data somewhere PHP can easily access it (like a database) and then write some logic into your php script to retrieve this data and display it.
  8. There should be zero business logic in controllers. They are nothing but a very thin layer between http and your domain.
  9. Yes they will be indexed by google.
  10. That is not a standard php error. Both CDbException & CDbCommand are part of your code base.
  11. Why would you care what mobile a client is using?
  12. There is no need to restart the machine, just the http server. sudo /etc/init.d/nginx restart
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.