我为什么不使用session
在考虑session的问题上,我最终放弃了session: 最后我选择了myql的heap表来处理session,并且把session处理和online在线用户统计结合起来。 下面给出代码为我的一个实例(没提供其他的细节了,具体使用要相应修改) `sid` char( 32 ) NOT NULL ,
1、原本的session是使用文件来管理的。文件系统的好坏直接影响session的性能,尤其当有几K人同时在线的时候,尤其突出。解决方法有两个:数据库和文件(使用哈希路径)。
2、原有session的扩展性和可控制性不好。不利于结合我现有的系统。
3、在选用数据库的时候,我并没有选择sqlite,上次我测试sqlite效率在win xp上效率没有想象中的好。
/**
* 处理在线用户和对session的模拟
* CREATE TABLE `webqq_session` (
`uid` mediumint( 8 ) NOT NULL ,
`username` char( 80 ) NOT NULL ,
`ismember` tinyint( 1 ) NOT NULL ,
`logintime` int( 10 ) NOT NULL ,
`activetime` int( 10 ) NOT NULL ,
PRIMARY KEY ( `sid` )
) ENGINE = HEAP DEFAULT CHARSET = gb2312
* @author:feifengxlq
* @since:2006-10-23
* @copyright:http://www.phpobject.net
* 注意:这个文件的使用必须和其他文件结合:比如对cookid的过滤,一些基本函数和数据库操作类
*/
class session
{
var $mysql;
var $cookie_id=webqq_sid;
var $session=array();
var $max_time=1200;//默认最大时间为20分钟
function __construct()
{
$this->mysql=new module(TB_PREX._session);//需要外部支持
$this->start();
}
function start()
{
if(empty($_COOKIE[$this->cookie_id]))
{
//初始化session
$this->create();
}else{
//cookie已经存在,检查是否存在数据库中
$sid=$_COOKIE[$this->cookie_id];
if($this->mysql->detail(where sid=.$sid.))
{
//存在数据库中
$row[activetime]=time();
$this->mysql->update($row,where sid=.$sid.);
$this->session=$this->mysql->detail(where sid=.$sid.);
}else{
//不存在数据库中
$this->create();
}
}
//删除数据库中不在线的用户
$this->mysql->delete(where activetime+.$this->max_time.<.time> }
function register($name,$value,$update=false)
{
if(array_key_exists($name,$this->session)){
$this->session[$name]=$value;
}
if($update)$this->update();
}
function registry($name=)
{
if(empty($name)) return $this->session;
if(array_key_exists($name,$this->session)){
return $this->session[$name];
}
}
//更新数据库里面的session信息
function update()
{
$row[uid]=$this->session[uid];
$row[username]=$this->session[username];
$row[ismember]=$this->session[ismember];
$row[logintime]=$this->session[logintime];
$row[activetime]=$this->session[activetime];
$this->mysql->update($row,where sid=.$this->session[sid].);
}
/*-------------------以下为私有方法------------------------------------------------------**/
function create()
{
$nowtime=time();
$sid=md5(0.$nowtime.getip());//需要预先定义好getip()函数:获取客户的IP地址
setcookie($this->cookie_id,$sid,$nowtime+3600*24);//默认24小时
$row[sid]=$sid;
$row[uid]=0;
$row[username]=guest;
$row[ismember]=0;
$row[logintime]=$nowtime;
$row[activetime]=$nowtime;
$this->mysql->add($row);//写入数据库
$this->session=$row;
}
}
?>

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The main reasons why you cannot log in to MySQL as root are permission problems, configuration file errors, password inconsistent, socket file problems, or firewall interception. The solution includes: check whether the bind-address parameter in the configuration file is configured correctly. Check whether the root user permissions have been modified or deleted and reset. Verify that the password is accurate, including case and special characters. Check socket file permission settings and paths. Check that the firewall blocks connections to the MySQL server.

It is impossible to view MongoDB password directly through Navicat because it is stored as hash values. How to retrieve lost passwords: 1. Reset passwords; 2. Check configuration files (may contain hash values); 3. Check codes (may hardcode passwords).

The kill command in MySQL sometimes fails because of the special process status and improper signal level. Methods to effectively terminate the MySQL process include: confirming the process status, using the mysqladmin command (recommended), using kill -9 with caution, checking system resources, and in-depth troubleshooting of error logs.

CentOS will be shut down in 2024 because its upstream distribution, RHEL 8, has been shut down. This shutdown will affect the CentOS 8 system, preventing it from continuing to receive updates. Users should plan for migration, and recommended options include CentOS Stream, AlmaLinux, and Rocky Linux to keep the system safe and stable.

Recovering deleted rows directly from the database is usually impossible unless there is a backup or transaction rollback mechanism. Key point: Transaction rollback: Execute ROLLBACK before the transaction is committed to recover data. Backup: Regular backup of the database can be used to quickly restore data. Database snapshot: You can create a read-only copy of the database and restore the data after the data is deleted accidentally. Use DELETE statement with caution: Check the conditions carefully to avoid accidentally deleting data. Use the WHERE clause: explicitly specify the data to be deleted. Use the test environment: Test before performing a DELETE operation.

Navicat for MariaDB cannot view the database password directly because the password is stored in encrypted form. To ensure the database security, there are three ways to reset your password: reset your password through Navicat and set a complex password. View the configuration file (not recommended, high risk). Use system command line tools (not recommended, you need to be proficient in command line tools).

It is impossible to view PostgreSQL passwords directly from Navicat, because Navicat stores passwords encrypted for security reasons. To confirm the password, try to connect to the database; to modify the password, please use the graphical interface of psql or Navicat; for other purposes, you need to configure connection parameters in the code to avoid hard-coded passwords. To enhance security, it is recommended to use strong passwords, periodic modifications and enable multi-factor authentication.

Reasons for Navicat connection timeout: network instability, busy database, firewall blocking, server configuration problems, and improper Navicat settings. Solution steps: Check network connection, database status, firewall settings, adjust server configuration, check Navicat settings, restart the software and server, and contact the administrator for help.
