PHP can open sockets on remote or local hosts. Here is a hands-on example of using such a socket: getting connected to a Usenet News Server, talking to this server, and downloading some articles for a precise newsgroup.

Opening a socket in PHP

Sockets are opened using fsockopen(). This function is both available in PHP3 and PHP4. It uses the following prototype :

<?php
int fsockopen
    (string hostname,
        int port [,
        int errno [,
        string errstr [,
        double timeout]]])
?>

 For the Internet domain, it will open a TCP socket connection to hostname on port port. hostname may in this case be either a fully qualified domain name or an IP address. For UDP connections, you need to explicitly specify the protocol: udp://hostname. For the Unix domain, hostname will be used as the path to the socket, port must be set to 0 in this case. The optional timeout can be used to set a timeout in seconds for the connect system call.

More information about fsockopen() : http://www.php.net/manual/function.fsockopen.php

Network News Transfer Protocol

Accessing a Usenet News Server requires using a specific protocol, called NNTP and standing for Network News Transfer Protocol.

This protocol is higly detailed in RFC977 (Request For Comment number 977), which is available at : http://www.w3.org/Protocols/rfc977/rfc977.html

This document described precisely how to connect to and then dialog with the NNTP server thanks to the various commands available for the task.

Connecting

Connecting to the NNTP server requires knowing its hostname (or IP address) and the port it is listening on. You should include a timeout so that an unsuccessful attempt at connecting does not “freeze” the application.
<?php
$cfgServer    = “your.news.host”;
$cfgPort    = 119;
$cfgTimeOut    = 10;// open a socket
if(!$cfgTimeOut)
    // without timeout
    $usenet_handle = fsockopen($cfgServer, $cfgPort);
else
    // with timeout
    $usenet_handle = fsockopen($cfgServer, $cfgPort, &$errno, &$errstr, $cfgTimeOut);if(!

$usenet_handle) {
    echo “Connexion failed\n”;
    exit();
}    
else {
    echo “Connected\n”;
    $tmp = fgets($usenet_handle, 1024);
}?>
Talking to the Server

We are now connected to the server, and can talk to it through th previously opened socket. Let us say we want to get the 10 latest articles from some newsgroup. RFC977 specifies that the first step is to select the right newsgroup with the GROUP command :

GROUP ggg

The required parameter ggg is the name of the newsgroup to be selected (e.g. “net.news”). A list of valid newsgroups may be obtained from the LIST command. The successful selection response will return the article numbers of the first and last articles in the group, and an estimate of the number of articles on file in the group.

Example:

chrome:~$ telnet my.news.host 119
Trying aa.bb.cc.dd…
Connected to my.news.host.
Escape character is ‘^]’.
200 my.news.host InterNetNews NNRP server INN 2.2.2 13-Dec-1999 ready (posting ok).
GROUP alt.test
211 232 222996 223235 alt.test
quit
205
After receiving the command ” GROUP alt.test”, the News Server answered “211 232 222996 223235 alt.test”. 211 is an RFC defined code (basically saying the command was succesfully executed – check the RFC for more details). It also answered it currently has 232 articles, indexed 222996 for the oldest through 223235 for the latest. These are called article numbers. Now, let us have a count here : 222996 + 232 by no means equals to 232235. The seven missing articles were removed one way or another from the server, either cancelled by their legitimate author (yes, it is possible and easy to do !) or deleted after report of abuse for example.
Be careful though, the server might require authentication before selecting the newsgroup, depending on wether it is a public or private server. It could also let anybody retrieve articles but require authentication to publish an article.

<?php//$cfgUser    = “xxxxxx”;
//$cfgPasswd    = “yyyyyy”;
$cfgNewsGroup    = “alt.php”;

// identification required on private server
if($cfgUser) {
    fputs($usenet_handle, “AUTHINFO USER “.$cfgUser.“\n”);
    $tmp = fgets($usenet_handle, 1024);    fputs($usenet_handle, “AUTHINFO PASS “.$cfgPasswd.“\n”);
    $tmp = fgets($usenet_handle, 1024);    

// check error
    
    if($tmp != “281 Ok\r\n”) {
        echo “502 Authentication error\n”;
        exit();
    }    
}// select newsgroup

fputs($usenet_handle, “GROUP “.$cfgNewsGroup.“\n”);
$tmp = fgets($usenet_handle, 1024);if($tmp == “480 Authentication required for command\r\n”) {
    echo “$tmp\n“;
    exit();
}    

$info = split(” “, $tmp);
$first = $info[2];
$last = $info[3]; print “First : $first\n“;
print “Last : $last\n“;?>

It can check if the cache with a certain key already exists. If it exists and it is not expired, it can return the cached data. Otherwise it can store newly generated data in a cache file with the given key.

The class can be configured to set the cache life time and the root directory of where all the cache files will be stored.

cachemanager.php

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
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

< ?php
class CacheManager extends Entity {
 
	/**
	* Contains number of seconds - timeframe for storing cache
	* @http://www.easemarry.com/blog
	* @var int
	* @name timeframe
	* @access private
	*/
	var $timeframe;
 
	/**
	* Contains name of the cache root directory 
	*
	* @var string
	* @name _cacheRoot
	* @access public
	*/
	var $_cacheRoot;
 
	/**
	* Constructor, defines timeframe for storing cache
	*
	* @param int number of seconds
	* @param int number of minutes
	* @param int number of hours
	* @param int number of days
	* @param int number of month
	* @param int number of years
	*/
	function CacheManager ($second = 0, $minute = 0, $hour = 0, $day = 0, $month = 0, $year = 0) {
		$this->timeframe = mktime (2 + $hour, 0 + $minute, 0 + $second, 1 + $month, 1 + $day, 1970 + $year);
	}
 
	/**
	* Checks if cache contains file no older than timeframe
	*
	* @return string
	*/
	function CheckCache ($model, $key = 0, $fname = '', $timeframe = 0) {
		$result   = 0;
		$filename = ($fname ? $fname : $this->_cacheRoot.strtolower($model).'/'.($key ? $key : 'model').'.html');
		if ( file_exists ($filename) ) {
			$tframe = ($timeframe ? $timeframe : $this->timeframe);
			if (time() - filemtime ($filename) < $tframe) $result = $this->RetrieveData ($filename);
		}
		return $result;
	}
 
	/**
	* Read the content of the file
	*
	* @param string filename
	* @return string
	*/
	function RetrieveData ($filename) {
		$fp      = fopen ($filename, 'r');
		$content = fread ($fp, filesize ($filename));
		fclose ($fp);
		return $content;
	}
 
	/**
	* Store content in the file
	*
	* @return string
	*/
	function SaveToCache ($model, $key = 0, $content = '', $fname = '') {
		$filename = ($fname ? $fname : $this->_cacheRoot.strtolower($model).'/'.($key ? $key : 'model').'.html');
		$fp       = fopen ($filename, 'w+');
		fwrite ($fp, $content);
		fclose ($fp);
		return $filename;
	}
 
}
?>

example.php

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
29
30
31

< ?php
/**
* This example represents how easily we can automate 
* caching of both news list, and single news using 
* CacheManager class
*/
 
function GetElement ($key) {
	/* return single news */
	return 'Full News Number '.$key;
}
 
function GetElements () {
	/* return news list */
	for ($i=1; $i&lt;11; $i++) $result .= '<a href="./?id='.$i.'">News '.$i.'<br / />';
	return $result;
}
 
include './cachemanager.php';
 
$key = (isset($_GET['id']) ? intval($_GET['id']) : 0);
$CacheManager = &new CacheManager (0, 5);
$CacheManager->_cacheRoot = './cache/';
$content = $CacheManager->CheckCache ('news', $key);
if (!$content) {
    $content = ($key ? GetElement ($key) : $this->GetElements());
    $CacheManager->SaveToCache ('news', $key, $content);
}
 
echo $content;
?>

Cookie Functions:
Write Cookies
Read Cookies
Delete Cookies

Use of this class is fairly simple.

Step 1: Include the class source in your php project using the require or include statement.
Step 2: Instance the cookie class by using the new keyword. The constructor uses these parameters
cookieName[string]{required} as the base name of the cookie
cookieTimeout[int]{required} as the time added the Unix timestamp to determine when a cookie expires
cookieSerialize[bool]{optional} default is false. If set to true then the cookies will be stored as a single serialized cookie.
cookiePath[string]{optional} default is “/” for root path you can set for sub-directory paths here if you wish.

The constructor also handles the switch over from individual cookies to serialzied cookies.

Step 3: Write a cookie

NOTE: It is important to remember that writing cookies must be done before any other output is sent to the browser.

The WriteCookie function takes as an array as an argument. This array should be built so that the name of the value name
is stored as the array element index and the value to be set is the element value
array[name] = value

Create one element for each value you want stored as a cookie.

Step 4: Read a cookie

NOTE: Of course you can read a cookie from the $_COOKIE array however you will lose out on the in built handling of serialized cookies.

You read a cookie’s value by calling the ReadCookie function which takes as its argument the value name and you will receive the
cookie value in return. If the value name is not present (this single cookie is not set or not in the serialized array) then a NULL
is returned.

It is best to store the value to a variable and then test for NULL by the is_null function.

Step 5: KillCookie

The KillCookie function allows you to delete a single cookie item or array element. It takes as its argument the value name to be deleted.

Step 6: DestroyAllCookies

Will go through all the cookies with the base name as set in the constructor and delete them.
The delete process for this and the KillCookie function is handled by setting the cookie’s expire date as the current Unix timestamp
- a large integer (several years).

Step 7: To change cookies from individual cookies to a serialized cookie
This is handled by changing the constructor’s cookieSerialize flag from false to true. It must be done when the cookieClass is
instanced or it will not function correctly.

If you have any comments or questions concerning this php class you may contact me at jrsofty@gmail.com

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
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100

< ?php
	// cookieClass
	// Copyright (C) 2005 JRSofty Programming.
	// http://jrsofty1.stinkbugonline.com
	// Licensed under GNU/GPL 
 
	class cookieClass{
 
		var $cName = '';
		var $cTime = '';
		var $cSerialize = false;		
		var $cPath = '';
 
		function cookieClass($cookieName, $cookieTimeout, $cookieSerialize = false, $cookiePath = "/"){
			$this->cName = $cookieName;
			$this->cTime = $cookieTimeout;
			$this->cSerialize = $cookieSerialize;
			$this->cPath = $cookiePath;
			// This should fix the issue if you have cookies set and THEN turn on the serialization.
			$iname = $this->cName . "_S";
			if($this->cSerialize && !isset($_COOKIE[$iname])){
				$cookArr = array();
				foreach($_COOKIE as $name=>$val){
					if(strpos($name,$this->cName) !== false ){ // make sure it is a cookie set by this application
						$subname = substr($name,strlen($this->cName) + 1);
						$cookArr[$subname] = $val;
						$this->KillCookie($name);
					}
				}
				$this->WriteCookie($cookArr);
			}
			// This is the opposite from above. changes a serialized cookie to multiple cookies without loss of data
			if(!$this->cSerialize && isset($_COOKIE[$iname])){
				$cookArr = unserialize($_COOKIE[$iname]);
				$this->KillCookie($iname);
				$this->WriteCookie($cookArr);
			}
 
 
		}
 
		function DestroyAllCookies(){
			foreach($_COOKIE as $name=>$val){
				if(strpos($name,$this->cName) !== false){
					$_COOKIE[$name] = NULL;
					$this->KillCookie($name);
				}
			}
		}
 
		function ReadCookie($item){
			if($this->cSerialize){
				$name = $this->cName . "_S";
				if(isset($_COOKIE[$name])){
					// handle the cookie as a serialzied variable
					$sCookie = unserialize($_COOKIE[$name]);
					if(isset($sCookie[$item])){
						return $sCookie[$item];
					}else{
						return NULL;
					}
				}else{
					return NULL;
				}
			}else{
				$name = $this->cName . "_" . $item;
				if(isset($_COOKIE[$name])){
					// handle the item as separate cookies
					return $_COOKIE[$name];
				}else{
					return NULL;
				}
			}	
		}
 
		function KillCookie($cName){
			$tStamp = time() - 432000;
			setcookie($cName,"",$tStamp,$this->cPath);
		}
 
		function WriteCookie($itemArr){
			if($this->cSerialize){					
				$sItems = serialize($itemArr);
				$name = $this->cName . "_S";
				$_COOKIE[$name] = $sItems;
				$tStamp = time() + $this->cTime;
				setcookie($name,$sItems,$tStamp,$this->cPath);
			}else{
				$tStamp = time() + $this->cTime;
				foreach($itemArr as $nam=>$val){
					$name = $this->cName . "_" . $nam;
					$_COOKIE[$name] = $val;
					setcookie($name,$val,$tStamp,$this->cPath);
				}e
			}
		}
 
 
	}
?>

In a previous post, I worked some with the Solar_Form class to create a login form. This just used simple input fields (text and password) to create the login form. I came to another part of my application where I needed a calendar helper to fill in some fields. I wanted to eliminate some of the user issues that could come with invalid dates being entered, so I opted to create a custom form field instead. The field is a normal text field, marked as READONLY with a link that launches a Javascript popup with the calendar picker.

First, we need a little structure – here’s how the application is structured (basically):

MyApp

  App

   Base

    Helper

     FormDate.php

    Layout

    Locale

    View

   Event

   Event.php

    Helper

    Layout

    Locale

    View

     index.php

There’s a few things involved here:

• The form helper class – FormDate.php
• The Event.php class (controller) where the form will be created
• The View for the Event controller to output the form and some Javascript

We’ll start with building the form since that’s more familiar territory:

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
29
30
31
32
33
34

 
class MySite_App_Event extends MySite_App_Base {
    protected   $_action_default = 'index';
    protected   $_layout   = 'default';
    protected   $_view  ='index';
    public    $forms; 
    public function actionIndex(){
        $form = Solar::factory('Solar_Form');
        $form->setElements(array(
            'event_title'=>array(
                'type'=>'text',
                'label'=>'Event Title',
                'require'=>true,
                'valid'=>array(
                    array('notBlank','Please enter an event title!')
                )
            ),
            'event_start'=>array(
                'type'   =>'date',
                'label'  =>'Start Date',
                'require'=>true,
                'valid'  =>array(
                    array('notBlank','Please select a start date!')
                )
            ),
            'sub'=>array(
                'type'=>'submit',
                'value'=>'create event'
            )
        ));
        $form->feedback=NULL;
        $this->forms['create_form']=$form;
    }
}

If you look close, you’ll spot something custom in there – on the event_start element, there’s a type of “date”. This how our special form helper is called. Solar does a little magic here – it looks at the types of each of the elements and looks in a few places for something that matches that type. Most of the elements are Solar’s default types so it falls back to the ones in the Solar directories. The “date” type, however, isn’t one of them and the app will break if you leave it like this.

So, what’s a developer to do? Well, create a custom form handler of course! This is where the FormDate.php file comes into play. Here’s what ours contains:

1
2
3
4
5
6
7
8
9
10
11
12

 
class MySite_App_Base_Helper_FormDate extends Solar_View_Helper_FormElement { 
    public function formDate($info){
        $this->_prepare($info);
        return '<input type="text"'
             . ' name="' . $this-/>_view->escape($this->_name) . '"'
             . ' value="' . $this->_view->escape($this->_value) . '"'
             . $this->_view->attribs($this->_attribs)
             . ' READONLY/> <a href="#" onClick="date_picker(''.$this->_view->escape($this->_name).'')">select</a>';
    }
 
}

If you’ve been checking out the default Solar form fields, this should look familiar – it’s a ripoff of the default text field form helper that Solar comes with. The only addition is the Javascript-powered link there at the end that calls the date_picker application.

There’s a few things that need to be in place to get this to work. First off, the class name needs to be the right “path” to the file. So, for our class it corresponds to MySite/App/Base/Helper to tell Solar where the file exists. If this isn’t right, Solar won’t be able to find and use the file. Next thing to look out for is the last part of the class name – FormDate for us. The second part of this is what Solar uses when the class is called. So, for example, we use FormDate because we want the type to be “date”. If we wanted one that was some kind of special field that works with Google’s Maps, we could use FormGoogle and define our custom form field inside it. Speaking of inside, the method’s name has to match the class name – FormDate and formDate – and takes in the information passed to it (including the field name, the value to fill it with and attributes it might have).

Because this file exists in the Base controller’s Helper directory and our Event class extends the Base, we can use it. Plus, by putting it up in the Base Helper directory, we can use it in other places in the site that extend Base.

Now we’ll move on to the last part of the equation – the View for the Event controller:

1
2
3
4
5
6
7
8
9
10

 
<script>
function date_picker(fname){
    elem=document.getElementById(fname);
    elem.value='08/14/1977';
}
</script> 
< ?php
echo $this->form($this->forms['create_form']);
?>

In the View above (our index.php file), we define the Javascript function our custom helper will use – date_picker – that takes in the element name. In a real application, this would be the place to interface with another page (or maybe even some sort of Ajax request) to let the user pick the date. As it stands, though, we’re just putting our predefined date in the field. The PHP part is simple, just an execution of the form.

Ideally, you’d put any and all Javascript in a few files out in the public directory of your application rather than in the view itself, but since we’re going for simplicity here I’ve just put it in the page itself.

So, there we go – a simple method to make a custom form handler that you can use anywhere in your application. It’s pretty easy to see how you can expand upon this to make just about any kind of custom form element that you might want…

Server:

1
2
3
4
5
6
7
8
9
10
11

function recieveFile($data){
$data=base64_decode($data);
$path='/my/file/path/img_out.gif';
$fp=fopen($path,'w+');
if($fp){ fwrite($fp,$data); fclose($fp); }
return strlen($data).'written';
}
$input = file_get_contents(”php://input”);
$server = new SoapServer('http://[my url here]/binary.wsdl',array('encoding'=>'ISO-8859-1'));
$server->addFunction('recieveFile');
$server->handle();

and the Client:

1
2
3
4
5
6
7
8
9
10
11

ini_set("soap.wsdl_cache_enabled", "0");
//send binary data
$client=new SoapClient('http://[my url here]/binary.wsdl',array('encoding'=>'ISO-8859-1'));
$data=file_get_contents('/my/file/path/img_to_send.gif');
$ret=$client->recieveFile(base64_encode($data));
print_r($ret);
[/code]
 
It's pretty basic - the client just reads in the file's information, runs it through a call to <a href="http://php.net/base64_encode">base64_encode</a> before it's sent off to the server. Once it's there a mirror call to <a href="http://php.net/base64_decode">base64_decode</a> gets the content back to normal and it's written out to the "img_out.gif" file on the remote server.
 
It's probably not the best way to do it, but its one that I've found that works quickly and easily. I tried to just send the binary data without base64 encoding it and it didn't want to cooperate (it was only getting the first chunk of data). I don't know how well it'll perform with larger files, though - we shall see.


<?php
function processUserInput($a, $b)
{
echo divide($a,$b);
}
function divide($c, $d)
{
print_r(debug_backtrace());
}
echo processUserInput(4,0);
?>
This will output the following one

Array (

[0] => Array     (

             [file] => PHPDocument1

             [line] => 5

             [function] => divide

             [args] => Array

                 (

                     [0] => 4

                     [1] => 0

                 )

          )

[1] => Array         (

             [file] => PHPDocument1

             [line] => 14

             [function] => processUserInput

             [args] => Array                 (

                     [0] => 4

                     [1] => 0

                 )

          )

[2] => Array         (

             [file] => /home/hasin/Zend/ZendStudio-5.5.0/bin/php5/dummy.php

             [line] => 1

             [args] => Array                 (

                     [0] => PHPDocument1

                 )

              [function] => include

         )

  )

1. Read the manual
I really can’t emphasize this enough – there’s a lot to be learned just reading the PHP manual. Especially check out the string and array functions. There’s a lot of functionality available right there, and often by reading through the manual you’ll find you’ve been reinventing the wheel in past projects when you could have just used a core function. The manual is your friend.

2. Browse through some code
PHP has a lot of open source code out there. So why not learn from it? Download an open source PHP application and have a read through the code. The bigger projects are probably better, as they’ll have more complex structures and systems in place but also more thorough documentation explaining it all. Check out SourceForge.net if you can’t find a good place to start.

3. Learn a new framework
There are more PHP frameworks out there than you’ve had hot dinners; a lot of them are open source and available online if you know where to look. Try the major ones first – phpframeworks.com has a good list. Your framework can never be entirely complete, your next job may require a different framework and you might just find the functionality of another comes in handy in one of your projects.

4. Research
You’ve probably heard a lot of terminology and discussed in the context of PHP web development. From OOP to MVC, KISS to DRY, YAML to INI, even REST to XML-RPC, there are hundreds of technical concepts out there that could directly relate to your work. You may have formed a basic understanding of them, but do you really know what they are or what they mean for you? Spend some time doing real research; Wikipedia is a good place to start. You’re bound to learn something new.

5. Learn OOP
Maybe this follows on a little from the previous point, but OOP is more important than you think. Do you really know about PHP5’s implementation OOP? For example, are you familiar with abstract classes, interfaces, the implements keyword, static methods and properties, the ‘protected’ access modifier? Even many experienced PHP developers fall down in this area. If you make use of the features of OOP, you could save yourself a lot of development time.

So there you have it. Five, straightforward yet significant ways to be a better PHP developer.

http://www.developertutorials.com/blog/web/5-ways-to-be-a-better-php-developer-36/

But if has used webeditor, how to guarantee that the user the data, simultaneously achieves safely (for example prevents the XSS crack), indeed is the headache question.

Here I recommend one to open the source tool – - KSES. KESS only permits the user input the data format and the attribute.

For example you only allowed the input saying

<a href=”" mce_href=”">
that
<a href=” ” title=”">
will include in that title to filter.

KSES is useful in WP and Gregarius, is a very easy to use thing. The use is also very simple, but is only not good, does not have the useful kind to seal, possibly this also has author own reason.

Example:

<?php
$kses_allowed = array (’address’ => array (),
‘a’ => array (’href’ => array (),
‘title’ => array (),
‘rel’ => array (),
‘rev’ => array (),
‘name’ => array ()),
‘abbr’ => array (’title’ => array ()),
‘acronym’ => array (’title’ => array ()),
‘b’ => array (),
‘big’ => array (),
‘blockquote’ => array (’cite’ => array ()),
‘br’ => array (),
‘button’ => array (’disabled’ => array (),
‘name’ => array (),
‘type’ => array (),
‘value’ => array ()),
‘caption’ => array (’align’ => array ()),
‘code’ => array (),
‘col’ => array (’align’ => array (),
‘char’ => array (),
‘charoff’ => array (),
’span’ => array (),
‘valign’ => array (),
‘width’ => array ()),
‘del’ => array (’datetime’ => array ()),
‘dd’ => array (),
‘div’ => array (’align’ => array ()),
‘dl’ => array (),
‘dt’ => array (),
‘em’ => array (),
‘fieldset’ => array (),
‘font’ => array (’color’ => array (),
‘face’ => array (),
’size’ => array ()),
‘form’ => array (’action’ => array (),
‘accept’ => array (),
‘accept-charset’ => array (),
‘enctype’ => array (),
‘method’ => array (),
‘name’ => array (),
‘target’ => array ()),
‘h1′ => array (’align’ => array ()),
‘h2′ => array (’align’ => array ()),
‘h3′ => array (’align’ => array ()),
‘h4′ => array (’align’ => array ()),
‘h5′ => array (’align’ => array ()),
‘h6′ => array (’align’ => array ()),
‘hr’ => array (’align’ => array (),
‘noshade’ => array (), ’size’ => array (),
‘width’ => array ()),
‘i’ => array (),
‘img’ => array (’alt’ => array (),
‘align’ => array (),
‘border’ => array (),
‘height’ => array (),
‘hspace’ => array (),
‘longdesc’ => array (),
‘vspace’ => array (),
’src’ => array (),
‘width’ => array ()),
‘ins’ => array (’datetime’ => array (),
‘cite’ => array ()),
‘kbd’ => array (),
‘label’ => array (’for’ => array ()),
‘legend’ => array (’align’ => array ()),
‘li’ => array (),
‘p’ => array (’align’ => array ()),
‘pre’ => array (’width’ => array ()),
‘q’ => array (’cite’ => array ()),
’s’ => array (),
’strike’ => array (),
’strong’ => array (),
’sub’ => array (),
’sup’ => array (),
‘table’ => array (’align’ => array (),
‘bgcolor’ => array (),
‘border’ => array (),
‘cellpadding’ => array (),
‘cellspacing’ => array (),
‘rules’ => array (),
’summary’ => array (),
‘width’ => array ()),
‘tbody’ => array (’align’ => array (),
‘char’ => array (), ‘charoff’ => array (),
‘valign’ => array ()),
‘td’ => array (’abbr’ => array (),
‘align’ => array (),
‘axis’ => array (),
‘bgcolor’ => array (),
‘char’ => array (),
‘charoff’ => array (),
‘colspan’ => array (),
‘headers’ => array (),
‘height’ => array (),
‘nowrap’ => array (),
‘rowspan’ => array (),
’scope’ => array (),
‘valign’ => array (),
‘width’ => array ()),
‘textarea’ => array (’cols’ => array (),
‘rows’ => array (), ‘disabled’ => array (),
‘name’ => array (),
‘readonly’ => array ()),
‘tfoot’ => array (’align’ => array (),
‘char’ => array (),
‘charoff’ => array (),
‘valign’ => array ()),
‘th’ => array (’abbr’ => array (),
‘align’ => array (),
‘axis’ => array (),
‘bgcolor’ => array (),
‘char’ => array (),
‘charoff’ => array (),
‘colspan’ => array (),
‘headers’ => array (),
‘height’ => array (),
‘nowrap’ => array (),
‘rowspan’ => array (),
’scope’ => array (),
‘valign’ => array (),
‘width’ => array ()),
‘thead’ => array (’align’ => array (),
‘char’ => array (),
‘charoff’ => array (),
‘valign’ => array ()),
‘title’ => array (),
‘tr’ => array (’align’ => array (),
‘bgcolor’ => array (),
‘char’ => array (),
‘charoff’ => array (),
‘valign’ => array ()),
‘tt’ => array (),
‘u’ => array (),
‘ul’ => array (),
‘ol’ => array (),
‘var’ => array ()
);
$string=kses($string, $kses_allowed);
?>

       If the overall situation in a document containing all of the class library, and then all the pages contain the whole document. Thus, although simplified the work, but has actually brought the efficiency drop. Because php will contain to each document to carry on the examination. Although the PHP efficiency is very high, but examines one big pile of kind, will bring some performance the drop, specially in a large-scale system.
        Has the method to be possible to satisfy both sides? Certainly there,The method is the factory pattern.
        We have established the following four documents.

index.php

In index.php, we passed a factory to create other instance,

In the factory, the preservation of an array $this->mClasses,format for the array ( “class name” => “class file path”).

We through the factory::create() to create an instance, in create(), the first test of whether to exist, if don’t exist, based on $this-> mClasses category corresponding to the type of document contains come. Then create and return a such examples.

Thus, we need only to factory-type document contains implementation of the script (example:index.php) on it.
        Everybody possibly also noted in t1.inc.php in two lines of code.
  Global $config;
  $Config = ’surfchen’;

        Why do we need global? Because t1.inc.php is include in factory::create, in the t1 document’s variables will approve the default function to the class. Therefore,we need one of the variables (example: $config) to index.php to global access to.
        Operation index.php, will be output
        Name:: T1surfchen

http://www.easemarry.com/blog/

First, code optimization

On a code optimization, perhaps you think is neat and clear code, but this is not the meaning of this, because if we seek rate, we should PHP source to be adjusted accordingly. Generally speaking is to remove redundant Notes, code unreadable. But this is a good accomplishment for programmers, it is inconceivable. Fortunately Zend Technologies announced the Zend engine optimization can help you do this. It is now free, but you must follow Zend Optimizer license. This product can be the engine optimized intermediate code.

This engine is relatively simple to install, download corresponding platform versions later, untied compressed files, and then in the php.ini file add the following two lines inside, restart the Web server, to get.

Zend_optimizer.optimization_level = 15
Zend_extension = “/ path / to / ZendOptimizer.so”
Zend_loader.enable = Off

If Win32 platform, it will be:

Zend_optimizer.optimization_level = 15
Zend_extension_ts = “C: /path / to / ZendOptimizer.dll”
Zend_loader.enable = Off

Ah! Not mistaken? How is three lines? In fact, the third line is optional. Seem to switch off because zend_loader can improve the speed, and is therefore worthy of this third line put php.ini. It must be noted that switching off is a prerequisite for the use of Zend you do not have encryption procedures.

Second, the buffer

If you want to further enhance the speed, we need to consider adopting buffer technology. Some optional solutions, including Zend Cache (test version), APC, and Afterburner Cache, such as another jpCache.

These are of a buffer module, the first time right. Php documents requested the intermediate code stored in the Web server’s memory, and then later on the request to return to “build good” version. This reduction of the disk to read and write, but in the memory, so this process can significantly improve application performance,

Off-the-shelf products such comparison, in the end choose whom?

Zend Cache is a good commercial product, in the first loading of those great PHP pages, you will clearly feel the speed increase, the server will leave more resources. Unfortunately, this product is to spend money, but in some cases, you may not mean the money.

Afterburner Cache is Bware Technologies products, is still in Beta version, and Zend Cashe appear to be the same, but it did not achieve good results Zend Cache, we can not and Zend engine optimization work together, but it is free, so I use this module.

APC (Alternative PHP Cache) is issued by the Community Connect has a free module can be used in production may seem environment.

Third, Web content compression

The increasingly crowded network, saving bandwidth like water conservation, is very much worth advocated. According to IETF standards, the majority of the browser should support the use of the contents of gzip compression. In other words you can use gzip compressed content sent to the browser, the browser will be transparent to extract the data.

Mod_gzip is Remote Communications Company introduced free Apache module, able to static Web content compression sent to the browser. For most static pages, this module is suitable. Although

Remotecommunications company said that this module supports all those who mod_php, mod_perl, mod what the dynamic content, but it still does not work, mod_gzip mailing list, the problem is estimated to 1.3.14.6 f can be resolved.

If the dynamic content compression, we can use class.gzip_encode.php, one in the script at the beginning and end of the use of PHP. For the entire site is in the php.ini auto_prepend and auto_append in which the function call. You can read the details of the procedures, which notes very well, and the author almost anything to tell you. But before use, your PHP to build support for the zlib.

For PHP 4.0.4, a new solution is the use of ob_gzhandler, to achieve the above categories and the same effect, as long as simple php.ini joined in the following sentence can be:

Output_handler = ob_gzhandler;

This allows PHP output caching, and compression of all output. If there is anything special reasons do not want to have all the contents of compressed output, can be used in the. Htaccess files by adding the following line in the corresponding directory under the file compression.

Php_value output_handler ob_gzhandler

Can be directly added to the code in PHP:

Ob_start ( “ob_gzhandler”);

The compression technology is very effective, but Netscape Communicator users, because Bunaiyasu graphics files, so do not seem to complete the jpeg and gif file compression, IE do not have this problem.

Conclusion:

This paper discussed the use of technology should be able to improve the performance of your site, but it should be noted that:

– PHP may not lead to bottlenecks reasons, carefully examined for other reasons (for example: Database)

– You can not regulate the server performance to the highest state. Therefore, in the buffer prior to complain of PHP and consider whether to upgrade the server, or to use dynamic load balancing technology.

– Do not underestimate the content compression, in your 100 Mb of internal online PHP applications that improve the speed, do not forget to use the modem users where 100 Kb blame your HTML page.

http://www.easemarry.com/blog