PHP Server-side Breakout

SERVER SIDE BREAKOUT
php

Wednesday, November 2, 11

5 YEARS AGO (2006)

PHP version 5.2.0
native JSON support


MODERN USAGE

77% of all websites


MODERN USAGE

Middleware


INTERFACES

REST
Ext.Direct


REST

Great for APIs
Cross-domain
Status code messages
One setup for all purposes

echo $json


REST

proxy: {
type: 'rest',
url: 'api/users'
}


REST

Extra server setup may be needed
Difﬁcult concurrency (buffering)
Requires access to php://input


EXT.DIRECT

OOB buffering
Effortless setup
API integration (RPC)
Easier RPC role-based method distribution

return $array


EXT.DIRECT

Ext.ns("Ext.app");
Ext.app.REMOTING_API = {
"url":"php/router.php",
"type":"remoting",
"actions":{
"TestAction":[
{"name":"doEcho","len":1}
]
}
};


EXT.DIRECT

proxy: {
type: 'direct',
directFn: doEcho
}


EXT.DIRECT

proxy: {
type: 'direct',
api: {
create : Rpc.users.Add,
read : Rpc.users.List,
update : Rpc.users.Update,
delete : Rpc.users.Delete
}


EXT.DIRECT

Not cross-domain friendly
Needs a router (s-s stack)
No ﬁle uploading
Exception stops execution


SAMPLE USAGE
RESTFUL INTERFACE


EXT.DIRECT


JSON VS. JSONP

{ Ext.util.JSONP.callback1({
‘name’ : ‘John’, ‘name’ : ‘John’,
‘email’ : ‘john@smith.com', ‘email’ : ‘john@smith.com',
‘dob‘ : 19781213, ‘dob‘ : 19781213,
‘kids‘ : [‘Sarah’, ‘Norah’] ‘kids‘ : [‘Sarah’, ‘Norah’]
} })


JSON VS. JSONP

$callback = $_REQUEST[“callback”];

$select = $db->select()->from('products');
$stmt = $select->query();
$result = $stmt->fetchAll();
$output = json_encode($result);

if ($callback) {
header('Content-Type: text/javascript');
echo $callback . '(' . $output . ');';
} else {
header('Content-Type: application/x-json');
echo $output;
}


BIG APPS

Big apps


BIG APPS

MVC
Fat model - thin controller


BIG APPS

Abstracting


LOADING APP COMPONENTS

Ext.Loader
Sencha command / jsbuilder on the ﬂy


ENVIRONMENT

Apache


ENVIRONMENT

Apache
+
Nginx reverse proxy


ENVIRONMENT

SetEnv APP_ENV "development"

$_SERVER['APP_ENV'])


ENVIRONMENT

MIME handling

JSONP : application/javascript
JSON : application/json
appcache : text/cache-manifest


ENVIRONMENT

File structure


ENVIRONMENT

DB layout


TRADITIONAL RELATIONAL
MODEL


CENTRALIZED RELATIONAL
MODEL


FIREPHP

$logger = new Zend_Log();
$writer = new Zend_Log_Writer_Firebug();
$logger->addWriter($writer);
Zend_Registry::set('logger',$logger);


FIREPHP

$select = $ssoDb->select() ->from('products');

$logger->log($select->__toString(), Zend_Log::INFO);
$logger->log($data, Zend_Log::INFO);


BAD IDEAS

Enclose entire class in a single try/catch block
Use sleep to wait for another task/thread to ﬁnish
Setting global vars to return multiple values
Altering framework ﬁles
Performing DB aggregate operations in PHP
Keeping connections open


BAD IDEAS

Using self-made cyphers for encryption
Clear text passwords, CC info, personal details (inc names)
Not checking for user credentials on every request
Trusting client-side input validation
Constructing sql queries by using concatenation
Not using DB transactions on multiple changes
Direct access to ﬁles for download


Grgur Grisogono
@ggrgur


PHP Server-side Breakout

More Related Content

What's hot

Similar to PHP Server-side Breakout

More from Sencha

Recently uploaded

PHP Server-side Breakout