因项目需要，需要记录用户未来3天的预约时间，每个预约时段为1小时。
例如：00:00:00～00:59:59 或 01:00:00～01:59:59 等为一个预约时段
前端代码如下：
提交预约日期 请选择预约时间：
后端代码如下：
true));?>
例如要提交某个用户的3天预约数据，所有时段都预约（全选）
后端收到的请求数据如下：
["2015-05-28 00:00:00","2015-05-28 01:00:00","2015-05-28 02:00:00","2015-05-28 03:00:00","2015-05-28 04:00:00","2015-05-28 05:00:00","2015-05-28 06:00:00","2015-05-28 07:00:00","2015-05-28 08:00:00","2015-05-28 09:00:00","2015-05-28 10:00:00","2015-05-28 11:00:00","2015-05-28 12:00:00","2015-05-28 13:00:00","2015-05-28 14:00:00","2015-05-28 15:00:00","2015-05-28 16:00:00","2015-05-28 17:00:00","2015-05-28 18:00:00","2015-05-28 19:00:00","2015-05-28 20:00:00","2015-05-28 21:00:00","2015-05-28 22:00:00","2015-05-28 23:00:00","2015-05-29 00:00:00","2015-05-29 01:00:00","2015-05-29 02:00:00","2015-05-29 03:00:00","2015-05-29 04:00:00","2015-05-29 05:00:00","2015-05-29 06:00:00","2015-05-29 07:00:00","2015-05-29 08:00:00","2015-05-29 09:00:00","2015-05-29 10:00:00","2015-05-29 11:00:00","2015-05-29 12:00:00","2015-05-29 13:00:00","2015-05-29 14:00:00","2015-05-29 15:00:00","2015-05-29 16:00:00","2015-05-29 17:00:00","2015-05-29 18:00:00","2015-05-29 19:00:00","2015-05-29 20:00:00","2015-05-29 21:00:00","2015-05-29 22:00:00","2015-05-29 23:00:00","2015-05-30 00:00:00","2015-05-30 01:00:00","2015-05-30 02:00:00","2015-05-30 03:00:00","2015-05-30 04:00:00","2015-05-30 05:00:00","2015-05-30 06:00:00","2015-05-30 07:00:00","2015-05-30 08:00:00","2015-05-30 09:00:00","2015-05-30 10:00:00","2015-05-30 11:00:00","2015-05-30 12:00:00","2015-05-30 13:00:00","2015-05-30 14:00:00","2015-05-30 15:00:00","2015-05-30 16:00:00","2015-05-30 17:00:00","2015-05-30 18:00:00","2015-05-30 19:00:00","2015-05-30 20:00:00","2015-05-30 21:00:00","2015-05-30 22:00:00","2015-05-30 23:00:00"]
请求数据content-length:2879
使用这种方式请求数据容量比较大，影响响应时间。
改进方法1:把DateTime格式时间转为时间戳再提交
前端代码修改如下：修改javascript fsubmit方法
后端收到的请求数据如下：
["1432742400","1432746000","1432749600","1432753200","1432756800","1432760400","1432764000","1432767600","1432771200","1432774800","1432778400","1432782000","1432785600","1432789200","1432792800","1432796400","1432800000","1432803600","1432807200","1432810800","1432814400","1432818000","1432821600","1432825200","1432828800","1432832400","1432836000","1432839600","1432843200","1432846800","1432850400","1432854000","1432857600","1432861200","1432864800","1432868400","1432872000","1432879200","1432882800","1432886400","1432890000","1432893600","1432897200","1432900800","1432904400","1432908000","1432911600","1432915200","1432918800","1432922400","1432926000","1432929600","1432933200","1432936800","1432940400","1432944000","1432947600","1432951200","1432954800","1432958400","1432962000","1432965600","1432969200","1432972800","1432976400","1432980000","1432983600","1432987200","1432990800","1432994400","1432998000"]
请求数据content-length:1916
后端收到后可把时间戳转为datetime格式使用
改进方法2:使用一个32位的整型变量，把每一小时作为32位整型的其中一位来存储
时段与32位整型的对应关系是
从右至左开始是00:00,01:00,02:00,03:00 以此类推，如果有选择的时段则为1，否则为0
例如：需要预约2016-05-28的 10:00,12:00,14:00,16:00,18:00
0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 忽略 忽略 忽略 忽略 忽略 忽略 忽略 忽略 23 22 21 20 19 18 17 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
则用32位二进制表示为 1010101010000000000 即10进制349184 ＝ 2的10次方 + 2的12次方 + 2的14次方 + 2的16次方 + 2的18次方
前端代码修改如下：修改javascript fsubmit方法
后端收到的请求数据如下：
["2015-05-28 16777215","2015-05-29 16777215","2015-05-30 16777215"]
请求数据content-length:107
使用这种方法，一天不管选了多少个预约时段，都只会有一条记录，大量减少提交的数据大小。
后端把10进制转换为时间的方法：
1.把10进制转为2进制，并反转
2.循环判断每一位，记录值为1的
3.记录保存
代码如下：
输出：
Array(
[0] => 2015-05-28 08:00:00
[1] => 2015-05-28 10:00:00
[2] => 2015-05-28 12:00:00
[3] => 2015-05-28 14:00:00
[4] => 2015-05-28 16:00:00
[5] => 2015-05-28 18:00:00
[6] => 2015-05-28 20:00:00)总结：本文提供一种可以把大量数据转换为小容量数据传输的方法，但需要加入更多的运算。因此实际开发中需根据实际需求来判断是否适合用时间换空间，或空间换时间的算法。
本篇文章讲解了优化客户端调用服务端接口减少请求数据容量，更多相关内容请关注php中文网。
相关推荐：
