Discussion on PHP + MySQL chat room technology

Talking about PHP + MySQL chat room technology, and reading about PHP + MySQL chat room technology. recently, the topic of PHP chat room technology has been launched in PHPChina. I am working on this project recently, I would like to share my personal views here. Main functions of the chat room: 1. Register, log on, exit, and modify information. & Nbs... "> <LINKhref =" http://www.php100.com

Recently, the topic of PHP chat room technology has been launched in PHPChina, and I am working on this project recently. I also want to express my views here.

Main functions of the chat room:
1. Register, log on, exit, and modify data.
2. the user applies to create a chat room and customize attributes of the chat room.
3. display the chat room name, description, host, announcement, and advertisement.
4. the online user list is displayed in real time. you can view online user information (such as nickname, email, ip address, and online duration ).
5. publish chat content, font attributes, actions, expressions, and common phrases.
6. allow stealth, private chat, scrolling, blocking users, clear screens, selection of chat scenarios, background music, and custom sending methods.
7. the administrator has the right to manage members (such as kicking out, disallowing speeches, and handing over management permissions ).

Note:
1. forbidden to use the framework structure (iframe does not bring any benefit except to reduce your Labor volume)
2. the front-end and back-end code are completely separated. only data is transmitted through the ajax channel, and only necessary data should be transmitted. (Display data at the front end and process data at the backend)
3. do not refresh the entire page caused by the program. only update the content that needs to be changed (do not use header or meta to refresh the page ).
4. when submitting chat content, you cannot blindly pursue the speed of user experience, but ignore the actual order of chat record submission. (That is to say, the submitted chat records should be reorganized on the server in the actual order and then transmitted to the client, because many people may submit information at the same time)

Technologies used:
1. AJAX, a bridge between the front and back ends. Jquery and XAJAX can be used. I prefer jquery, which is fast, simple, and durable. There are many plug-ins that can be updated quickly.
2. the data carrier form is XML. In fact, the data in common chat rooms is not very complex, and json is enough.
3. database abstraction layer-ADODB. Using PDO is faster. I am used to using ADODB.
4. MySQL, the underlying data storage medium. There is no doubt about this.
5. Data intermediate storage medium-memcache. Store high-speed read/write data in the memcache shared memory to reduce the load on the database.
6. if you want to implement video and voice, you need to install flash player on the client side, which is supported by the server-side PostgreSQL (flash media server. It also involves data interaction between html, javascript, flash, and the background. There are not many materials in this regard.

These are the core technologies. in actual application development, many details need to be solved.

For example, how to update the online list?
There are two ways:
1. refresh the entire list (whether updated or not ).
2. add new online members, delete offline members, and change materials.
Obviously, the second option is the best choice.

How can I handle the XmlHttpRequest concurrency problem?
Javascript is single-threaded. if there are two XmlHttpRequest objects at the same time, it is very prone to problems. This requires us to control the generation and termination of XmlHttpRequest.
In chat rooms, the data we need to update mainly includes the online list (including member information updates), chat records, and chat room attributes. The update frequency is inconsistent (if the time is the same, you only need to create an XmlHttpRequest to process it ). The chat record needs to be updated in a short period of time, and the online list can be updated for a little longer. If the XmlHttpRequest object is created separately without the framework, concurrency may occur. This requires the creation of a time and flow control function.
SetInterval ('process _ control () ', 3000) // call once every three seconds
The process_control function schedules tasks. for example, if a task is executed at a certain interval, the next task is executed only after the task is completed.