Orange juice

There was a man that wants to put a new business, the first and only rule was: It must to be simple.

As the time pass he though that selling orange juice will be the simplest and profiting business because he lives near of an orange farm so he could go and talk with the farmer and get a very good price.

So the business starts and this is what it happened.

DAY ONE:

1. One employee
2. Six customers
3. Four sales
4. Two customer asking for apple juice

DAY TWO:

1. One employee
2. Twenty customers
3. Fifteen sales
4. Five customers asking for apple juice

DAY THREE:

1. One employee
2. Forty customers
3. Twenty eight sales
4. Twelve customers asking for apple juice

At this point of the business the owner knows that he can’t continue working by itself so he hire more people to work at the company (yes now is a company).

DAY FOUR:

1. The sales team (One employee)
2. The squeeze team (Two employees)
3. Eighty customers
4. Seventy one sales
5. Nine customers asking for apple juice

There was a problem, several customers complains about their juice, they said the juice taste bad. So new team was created.

DAY FIVE:

1. The sales team (One employee)
2. The squeeze team (Two employees)
3. The quality assurance team (Two employees)
4. The customers were a lot
5. There was still people asking for apple juice

The owner hire more and more people, create new teams with funny names, the owner doesn’t even go to the juice place because he was busy with other company duties.

DAY TWENTY EIGHT:

1. The sales team (Four employees)
2. The squeeze team (Twelve employees)
3. The quality assurance team (Seven employees)
4. The accountant team (Two employees)
5. More teams.
6. More and more people asking for apple juice (what’s wrong with this people)

At the end he even hire consulting groups.

The conclusion is: “No meter how simple the things starts, you always finish with a complete mess and people asking for apple juice (Seriously, what’s wrong with this people).”

Normalmente el Singleton se utiliza cuando se requiere conservar propiedades durante el tiempo de vida de la applicación, es decir, en lo que dura la ejecución de la página actual.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

<?php 
class UsersOnline
{
	private $arrUsers = array();
	private static $oInstance;
 
	private function __construct() { }
 
	public static function getInstance()
	{
		if (empty(self::$oInstance)) {
			self::$oInstance = new UsersOnline();
		}
 
		return self::$oInstance;
	}
 
	public function setUser($numId, $oUser)
	{
		$this->arrUsers[$numId] = $oUser;  
	}
 
	public function getUser($numId)
	{
		return $this->arrUsers[$numId];
	}
}
?>

Ahora veamos como se utiliza por medio de un pequeño trozo de código.

1
2
3
4
5
6
7
8
9
10

<?php
include_once './UsersOnline.php';
 
$oSingleton = UsersOnline::getInstance();
$oSingleton->setUser(12345, array('name' => 'jorge'));
 
unset($oSingleton);
 
$oOtherInstance = UsersOnline::getInstance();
var_dump($oOtherInstance->getUser(12345));

La salida del script anterior nos muestra que aunque se boro la instancia $oSingleton por medio de unset(), las propiedades siguen aun existiendo.

array(1) {
  ["name"]=>
  string(5) "jorge"
}

Las platicas estuvieron geniales, aquí les dejo unas cuantas fotos del evento.