虽然两者都实现了html5 sse,但是两者处理方式是不同的。
若在服务器端处理的时候。若没有返回数据,在FF下会中断SSE连接,并且都不会在连接上了。
因此必须每次连接都有返回数据才行。而在CHROME下则可以处理这种情况。没有返回也可以再次发起连接。
Fireforx上sse是每5秒发起一次连接。而chrome是3秒。
Chrome:
Sat Oct 12 2013 16:36:06 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed article.js:2075
Sat Oct 12 2013 16:36:09 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed article.js:2075
Sat Oct 12 2013 16:36:12 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed article.js:2075
Sat Oct 12 2013 16:36:16 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
Firefox:
Date {Sat Oct 12 2013 16:36:29 GMT+0800}
article.js (line 2067)
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
article.js (line 2075)
Date {Sat Oct 12 2013 16:36:34 GMT+0800}
article.js (line 2067)
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
article.js (line 2075)
Date {Sat Oct 12 2013 16:36:39 GMT+0800}
article.js (line 2067)
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
SSE的缺点是,定制性不高,API的参数很少,比如不能自定义轮询的时间间隔。
它本质上就是轮询get 类型的AJAX。
在特定的需求下会比较有用,比如做个时间显示。如果用JS写,不能保证时间一致,用服务器端推送时间就能保证每个客户端的时间都是一致的。还有,比如间隔消息推送之类的需求。
若在服务器端处理的时候。若没有返回数据,在FF下会中断SSE连接,并且都不会在连接上了。
public function sse_connect()
{
header('Content-Type: text/event-stream');
header('Cache-Control: no-cache');
$result = D("Plan")->checkIsUpdate($_GET['planID'], $_GET['editTime']);
if ($result == "update") {
echo "event: update\n\n";
echo "data: {$result}\n\n";
ob_flush();
flush();
}
}
因此必须每次连接都有返回数据才行。而在CHROME下则可以处理这种情况。没有返回也可以再次发起连接。
Fireforx上sse是每5秒发起一次连接。而chrome是3秒。
Chrome:
Sat Oct 12 2013 16:36:06 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed article.js:2075
Sat Oct 12 2013 16:36:09 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed article.js:2075
Sat Oct 12 2013 16:36:12 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed article.js:2075
Sat Oct 12 2013 16:36:16 GMT+0800 (中国标准时间) article.js:2067
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
Firefox:
Date {Sat Oct 12 2013 16:36:29 GMT+0800}
article.js (line 2067)
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
article.js (line 2075)
Date {Sat Oct 12 2013 16:36:34 GMT+0800}
article.js (line 2067)
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
article.js (line 2075)
Date {Sat Oct 12 2013 16:36:39 GMT+0800}
article.js (line 2067)
http://pageplan/Portal/Article/sse_connect?planID=147&editTime=2013-10-12%2016:31:29connection is closed
SSE的缺点是,定制性不高,API的参数很少,比如不能自定义轮询的时间间隔。
它本质上就是轮询get 类型的AJAX。
在特定的需求下会比较有用,比如做个时间显示。如果用JS写,不能保证时间一致,用服务器端推送时间就能保证每个客户端的时间都是一致的。还有,比如间隔消息推送之类的需求。