| { | |
| "name": "spakkionu/validate", | |
| "description": "Validation Test", | |
| "require": { | |
| "illuminate/validation": "~4.2.9" | |
| }, | |
| "license": "MIT", | |
| "authors": [ | |
| { | |
| "name": "Jonathan Bernardi", |
| <!DOCTYPE html> | |
| <meta charset="utf-8"> | |
| <style> body { font-family: sans-serif; } </style> | |
| <body> | |
| <script src="require.js"></script> | |
| <script> | |
| require.config({ | |
| paths: { | |
| d3: "http://d3js.org/d3.v3.min" | |
| } |
| sudo -i | |
| cd | |
| apt-get install build-essential checkinstall && apt-get build-dep imagemagick -y | |
| wget http://www.imagemagick.org/download/ImageMagick-6.8.7-7.tar.gz | |
| tar xzvf ImageMagick-6.8.9-1.tar.gz | |
| cd ImageMagick-6.8.9-1/ | |
| ./configure --prefix=/opt/imagemagick-6.8 && make | |
| checkinstall |
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
| class Ticket < ActiveRecord::Base | |
| belongs_to :grouper | |
| belongs_to :user | |
| validate :user_cant_be_blacklisted, on: :confirmation | |
| validate :user_cant_double_book, on: :confirmation | |
| validate :grouper_cant_be_full, on: :confirmation | |
| validate :grouper_cant_have_occurred, on: :confirmation |
| ## Sample Propel configuration file ## | |
| propel: | |
| ## General settings ## | |
| general: | |
| # The name of your project. | |
| # This affects names of generated files, etc. | |
| project: | |
| version: 2.0.0-dev |
| <?php | |
| /* | |
| * Plugin: StreamlineFoundation | |
| * | |
| * Class: Schedule | |
| * | |
| * Description: Provides scheduling mechanics including creating a schedule, testing if a specific moment is part of the schedule, moving back | |
| * and forth between scheduled moments in time and translating the created schedule back to a human readable form. | |
| * | |
| * Usage: ::fromCronString() creates a new Schedule class and requires a string in the cron ('* * * * *', $language) format. |
This is just a small post in response to [this tweet][tweet] by Julien Pauli (who by the way is the release manager for PHP 5.5). In the tweet he claims that objects use more memory than arrays in PHP. Even though it can be like that, it's not true in most cases. (Note: This only applies to PHP 5.4 or newer.)
The reason why it's easy to assume that objects are larger than arrays is because objects can be seen as an array of properties and a bit of additional information (like the class it belongs to). And as array + additional info > array it obviously follows that objects are larger. The thing is that in most cases PHP can optimize the array part of it away. So how does that work?
The key here is that objects usually have a predefined set of keys, whereas arrays don't:
| Apache James 2.3.2, delivering to a local user, default setup | |
| $ time /usr/libexec/postfix/smtp-source -c -l 5000 -t testuser@localhost -s 100 -m 10000 127.0.0.1:25 | |
| 10000 | |
| real 1m5.751s | |
| user 0m0.630s | |
| sys 0m1.945s | |
