2. 程式人生 > >RTSP 互動過程

RTSP 互動過程

阿新 • • 發佈：2019-01-04
04-28 11:52:12.729: I/RTSPServer_jni(741): [live555android.cpp:296 void announceStream(RTSPServer*, ServerMediaSession*, char const*)]: Play this stream using the URL rtsp://192.168.100.102:8554/1
04-28 11:52:48.473: I/RTSPServer_jni(741): [RTSPServer.cpp:431 void RTSPServer::incomingConnectionHandler(int)]: accept()ed connection from 192.168.100.103
04-28 11:52:48.484: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x5560e858]::handleRequestBytes() read 134 new bytes:DESCRIBE rtsp://192.168.100.102:8554/1 RTSP/1.0
04-28 11:52:48.484: I/RTSPServer_jni(741): CSeq: 2
04-28 11:52:48.484: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:52:48.484: I/RTSPServer_jni(741): Accept: application/sdp
04-28 11:52:48.484: I/RTSPServer_jni(741):
04-28 11:52:48.484: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "DESCRIBE", urlPreSuffix "", urlSuffix "1", CSeq "2", Content-Length 0, with 0 bytes following the message.
04-28 11:52:51.995: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:52:51.995: I/RTSPServer_jni(741): CSeq: 2
04-28 11:52:51.995: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:52:51 GMT
04-28 11:52:51.995: I/RTSPServer_jni(741): Content-Base: rtsp://192.168.100.102:8554/1/
04-28 11:52:51.995: I/RTSPServer_jni(741): Content-Type: application/sdp
04-28 11:52:51.995: I/RTSPServer_jni(741): Content-Length: 471
04-28 11:52:51.995: I/RTSPServer_jni(741):
04-28 11:52:51.995: I/RTSPServer_jni(741): v=0
04-28 11:52:51.995: I/RTSPServer_jni(741): o=- 1493351532727360 1 IN IP4 192.168.100.102
04-28 11:52:51.995: I/RTSPServer_jni(741): s=Session streamed by "RTSPServer"
04-28 11:52:51.995: I/RTSPServer_jni(741): i=1
04-28 11:52:51.995: I/RTSPServer_jni(741): t=0 0
04-28 11:52:51.995: I/RTSPServer_jni(741): a=tool:LIVE555 Streaming Media v2014.07.18
04-28 11:52:51.995: I/RTSPServer_jni(741): a=type:broadcast
04-28 11:52:51.995: I/RTSPServer_jni(741): a=control:*
04-28 11:52:51.995: I/RTSPServer_jni(741): a=range:npt=0-
04-28 11:52:51.995: I/RTSPServer_jni(741): a=x-qt-text-nam:Session streamed by "RTSPServer"
04-28 11:52:51.995: I/RTSPServer_jni(741): a=x-qt-text-inf:1
04-28 11:52:51.995: I/RTSPServer_jni(741): m=video 0 RTP/AVP 96
04-28 11:52:51.995: I/RTSPServer_jni(741): c=IN IP4 0.0.0.0
04-28 11:52:51.995: I/RTSPServer_jni(741): b=AS:500
04-28 11:52:51.995: I/RTSPServer_jni(741): a=rtpmap:96 H264/90000
04-28 11:52:51.995: I/RTSPServer_jni(741): a=fmtp:96 packetization-mode=1;profile-level-id=42C01E;sprop-parameter-sets=Z0LAHrkQFAe0IAAAAwAgAAAFEeLF1A==,aM48gA==
04-28 11:52:51.995: I/RTSPServer_jni(741): a=control:track1
04-28 11:52:52.086: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x5560e858]::handleRequestBytes() read 165 new bytes:SETUP rtsp://192.168.100.102:8554/1/track1 RTSP/1.0
04-28 11:52:52.086: I/RTSPServer_jni(741): CSeq: 3
04-28 11:52:52.086: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:52:52.086: I/RTSPServer_jni(741): Transport: RTP/AVP;unicast;client_port=53474-53475
04-28 11:52:52.086: I/RTSPServer_jni(741):
04-28 11:52:52.087: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "SETUP", urlPreSuffix "1", urlSuffix "track1", CSeq "3", Content-Length 0, with 0 bytes following the message.
04-28 11:52:52.125: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:52:52.125: I/RTSPServer_jni(741): CSeq: 3
04-28 11:52:52.125: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:52:52 GMT
04-28 11:52:52.125: I/RTSPServer_jni(741): Transport: RTP/AVP;unicast;destination=192.168.100.103;source=192.168.100.102;client_port=53474-53475;server_port=6970-6971
04-28 11:52:52.125: I/RTSPServer_jni(741): Session: DB761C12;timeout=65
04-28 11:52:52.125: I/RTSPServer_jni(741):
04-28 11:52:52.160: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x5560e858]::handleRequestBytes() read 144 new bytes:PLAY rtsp://192.168.100.102:8554/1/ RTSP/1.0
04-28 11:52:52.160: I/RTSPServer_jni(741): CSeq: 4
04-28 11:52:52.160: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:52:52.160: I/RTSPServer_jni(741): Session: DB761C12
04-28 11:52:52.160: I/RTSPServer_jni(741): Range: npt=0.000-
04-28 11:52:52.160: I/RTSPServer_jni(741):
04-28 11:52:52.160: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "PLAY", urlPreSuffix "1", urlSuffix "", CSeq "4", Content-Length 0, with 0 bytes following the message.
04-28 11:52:52.162: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:52:52.162: I/RTSPServer_jni(741): CSeq: 4
04-28 11:52:52.162: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:52:52 GMT
04-28 11:52:52.162: I/RTSPServer_jni(741): Range: npt=0.000-
04-28 11:52:52.162: I/RTSPServer_jni(741): Session: DB761C12
04-28 11:52:52.162: I/RTSPServer_jni(741): RTP-Info: url=rtsp://192.168.100.102:8554/1/track1;seq=15867;rtptime=2124151534
04-28 11:52:52.162: I/RTSPServer_jni(741):
04-28 11:52:54.227: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "DB761C12", stream name "1"): Liveness indication
04-28 11:52:57.056: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "DB761C12", stream name "1"): Liveness indication
04-28 11:53:01.574: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "DB761C12", stream name "1"): Liveness indication
04-28 11:53:02.490: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "DB761C12", stream name "1"): Liveness indication
04-28 11:53:02.490: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x5560e858]::handleRequestBytes() read 129 new bytes:TEARDOWN rtsp://192.168.100.102:8554/1/ RTSP/1.0
04-28 11:53:02.490: I/RTSPServer_jni(741): CSeq: 5
04-28 11:53:02.490: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:53:02.490: I/RTSPServer_jni(741): Session: DB761C12
04-28 11:53:02.490: I/RTSPServer_jni(741):
04-28 11:53:02.490: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "TEARDOWN", urlPreSuffix "1", urlSuffix "", CSeq "5", Content-Length 0, with 0 bytes following the message.
04-28 11:53:02.490: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:53:02.490: I/RTSPServer_jni(741): CSeq: 5
04-28 11:53:02.490: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:53:02 GMT
04-28 11:53:02.490: I/RTSPServer_jni(741):
04-28 11:53:02.491: I/RTSPServer_jni(741): [RTSPServer.cpp:882 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x5560e858]::handleRequestBytes() read -1 new bytes (of 10000); terminating connection!
04-28 11:53:20.629: I/RTSPServer_jni(741): [RTSPServer.cpp:431 void RTSPServer::incomingConnectionHandler(int)]: accept()ed connection from 192.168.100.103
04-28 11:53:20.636: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x567cc268]::handleRequestBytes() read 134 new bytes:DESCRIBE rtsp://192.168.100.102:8554/1 RTSP/1.0
04-28 11:53:20.636: I/RTSPServer_jni(741): CSeq: 2
04-28 11:53:20.636: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:53:20.636: I/RTSPServer_jni(741): Accept: application/sdp
04-28 11:53:20.636: I/RTSPServer_jni(741):
04-28 11:53:20.636: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "DESCRIBE", urlPreSuffix "", urlSuffix "1", CSeq "2", Content-Length 0, with 0 bytes following the message.
04-28 11:53:20.636: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:53:20.636: I/RTSPServer_jni(741): CSeq: 2
04-28 11:53:20.636: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:53:20 GMT
04-28 11:53:20.636: I/RTSPServer_jni(741): Content-Base: rtsp://192.168.100.102:8554/1/
04-28 11:53:20.636: I/RTSPServer_jni(741): Content-Type: application/sdp
04-28 11:53:20.636: I/RTSPServer_jni(741): Content-Length: 471
04-28 11:53:20.636: I/RTSPServer_jni(741):
04-28 11:53:20.636: I/RTSPServer_jni(741): v=0
04-28 11:53:20.636: I/RTSPServer_jni(741): o=- 1493351532727360 1 IN IP4 192.168.100.102
04-28 11:53:20.636: I/RTSPServer_jni(741): s=Session streamed by "RTSPServer"
04-28 11:53:20.636: I/RTSPServer_jni(741): i=1
04-28 11:53:20.636: I/RTSPServer_jni(741): t=0 0
04-28 11:53:20.636: I/RTSPServer_jni(741): a=tool:LIVE555 Streaming Media v2014.07.18
04-28 11:53:20.636: I/RTSPServer_jni(741): a=type:broadcast
04-28 11:53:20.636: I/RTSPServer_jni(741): a=control:*
04-28 11:53:20.636: I/RTSPServer_jni(741): a=range:npt=0-
04-28 11:53:20.636: I/RTSPServer_jni(741): a=x-qt-text-nam:Session streamed by "RTSPServer"
04-28 11:53:20.636: I/RTSPServer_jni(741): a=x-qt-text-inf:1
04-28 11:53:20.636: I/RTSPServer_jni(741): m=video 0 RTP/AVP 96
04-28 11:53:20.636: I/RTSPServer_jni(741): c=IN IP4 0.0.0.0
04-28 11:53:20.636: I/RTSPServer_jni(741): b=AS:500
04-28 11:53:20.636: I/RTSPServer_jni(741): a=rtpmap:96 H264/90000
04-28 11:53:20.636: I/RTSPServer_jni(741): a=fmtp:96 packetization-mode=1;profile-level-id=42C01E;sprop-parameter-sets=Z0LAHrkQFAe0IAAAAwAgAAAFEeLF1A==,aM48gA==
04-28 11:53:20.636: I/RTSPServer_jni(741): a=control:track1
04-28 11:53:20.692: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x567cc268]::handleRequestBytes() read 165 new bytes:SETUP rtsp://192.168.100.102:8554/1/track1 RTSP/1.0
04-28 11:53:20.692: I/RTSPServer_jni(741): CSeq: 3
04-28 11:53:20.692: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:53:20.692: I/RTSPServer_jni(741): Transport: RTP/AVP;unicast;client_port=55586-55587
04-28 11:53:20.692: I/RTSPServer_jni(741):
04-28 11:53:20.692: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "SETUP", urlPreSuffix "1", urlSuffix "track1", CSeq "3", Content-Length 0, with 0 bytes following the message.
04-28 11:53:20.693: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:53:20.693: I/RTSPServer_jni(741): CSeq: 3
04-28 11:53:20.693: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:53:20 GMT
04-28 11:53:20.693: I/RTSPServer_jni(741): Transport: RTP/AVP;unicast;destination=192.168.100.103;source=192.168.100.102;client_port=55586-55587;server_port=6970-6971
04-28 11:53:20.693: I/RTSPServer_jni(741): Session: 350E6356;timeout=65
04-28 11:53:20.693: I/RTSPServer_jni(741):
04-28 11:53:20.714: I/RTSPServer_jni(741): [RTSPServer.cpp:897 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: RTSPClientConnection[0x567cc268]::handleRequestBytes() read 144 new bytes:PLAY rtsp://192.168.100.102:8554/1/ RTSP/1.0
04-28 11:53:20.714: I/RTSPServer_jni(741): CSeq: 4
04-28 11:53:20.714: I/RTSPServer_jni(741): User-Agent: LIVE555 Streaming Media v2012.01.13
04-28 11:53:20.714: I/RTSPServer_jni(741): Session: 350E6356
04-28 11:53:20.714: I/RTSPServer_jni(741): Range: npt=0.000-
04-28 11:53:20.714: I/RTSPServer_jni(741):
04-28 11:53:20.714: I/RTSPServer_jni(741): [RTSPServer.cpp:984 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: parseRTSPRequestString() succeeded, returning cmdName "PLAY", urlPreSuffix "1", urlSuffix "", CSeq "4", Content-Length 0, with 0 bytes following the message.
04-28 11:53:20.715: I/RTSPServer_jni(741): [RTSPServer.cpp:1123 void RTSPServer::RTSPClientConnection::handleRequestBytes(int)]: sending response: RTSP/1.0 200 OK
04-28 11:53:20.715: I/RTSPServer_jni(741): CSeq: 4
04-28 11:53:20.715: I/RTSPServer_jni(741): Date: Fri, Apr 28 2017 03:53:20 GMT
04-28 11:53:20.715: I/RTSPServer_jni(741): Range: npt=0.000-
04-28 11:53:20.715: I/RTSPServer_jni(741): Session: 350E6356
04-28 11:53:20.715: I/RTSPServer_jni(741): RTP-Info: url=rtsp://192.168.100.102:8554/1/track1;seq=30273;rtptime=3974772570
04-28 11:53:20.715: I/RTSPServer_jni(741):
04-28 11:53:24.193: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "350E6356", stream name "1"): Liveness indication
04-28 11:53:28.244: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "350E6356", stream name "1"): Liveness indication
04-28 11:53:34.027: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "350E6356", stream name "1"): Liveness indication
04-28 11:53:39.045: I/RTSPServer_jni(741): [RTSPServer.cpp:2144 static void RTSPServer::RTSPClientSession::noteClientLiveness(RTSPServer::RTSPClientSession*)]: RTSP client session (id "350E6356", stream name "1"): Liveness indication


相關推薦

RTSP 互動過程

04-28 11:52:12.729: I/RTSPServer_jni(741): [live555android.cpp:296 void announceStream(RTSPServer*, ServerMediaSession*, char const*)]: Play this stream us

RTSP 協議 簡單互動過程

Real Time Streaming Protocol或者RTSP（實時流媒體協議），是由Real network 和 Netscape共同提出的如何有效地在IP網路上傳輸流媒體資料的應用層協議。RTSP提供一 種可擴充套件的框架，使能夠提供可控制的，按需傳輸實時資料，

RTSP 協議 簡單互動過程

Real Time Streaming Protocol或者RTSP（實時流媒體協議），是由Real network 和 Netscape共同提出的如何有效地在IP網路上傳輸流媒體資料的應用層協議。RTSP提供一 種可擴充套件的框架，使能夠提供可控制的，按需傳輸實時資料，

ISO 14443 Type A卡的互動過程

分享一下我老師大神的人工智慧教程！零基礎，通俗易懂！http://blog.csdn.net/jiangjunshow 也歡迎大家轉載本篇文章。分享知識，造福人民，實現我們中華民族偉大復興！        

關於namenode、datanode和secondarynamenode的互動過程

元資料是儲存在namenode中的，這些元資料包括檔名、目錄名，檔案目錄從屬關係、檔案大小，檔案與塊對應關係，塊所對應的節點等；namenode會將這些元資料資訊儲存在硬碟上，對應的名字是fsimage_txid（即類似這種：fsimage_00000000000000321

從java 理解http互動過程，三次握手四次揮手

ip 網絡卡地址 本機 192.168.8.50 C8-5B-76-03-AC-5B 伺服器 192.168

大資料之hbase（一） --- HBase介紹，特性，安裝部署，shell命令，client端與hbase的互動過程，程式設計API訪問hbase實現百萬寫入

一、HBase介紹 ---------------------------------------------- 1.基於hadoop的資料庫，具有分散式，可伸縮的大型資料儲存 2.用於對資料的隨機訪問，實時讀寫 3.巨大的表，十億行*百萬列

iOS 一個HTTPS連線的客戶端與服務端互動過程

在一個HTTPS連線的網路中，輸入賬號和密碼並單擊登陸按鈕後，到伺服器返回這個請求前，這期間經歷了什麼？ 答：具體經歷了一下8步： 客戶端打包請求。其中包括URL、埠、賬號和密碼等。使用賬號和密碼登陸應該用的是POST方式，所以相關的使用者資訊會被載入到body中。這個請

微信小程式 互動過程中物件陣列賦值

舉個例子 這個留言框在wxml頁面只寫了一個 但是如果是多店鋪的購買 他就會迴圈出現多次  每次輸入店鋪留言 只會儲存最後一個input的內容但是後臺要拿到多個內容 <!-- 留言 --> <view class='conten

802.11協議幀格式、Wi-Fi連線互動過程、無線破解入門研究

目錄 1. 802.11標準簡介 2. 802.11協議格式 3. Wi-Fi認證過程 4. 802.11標準中的資料安全加密協議 1. 802.11標準簡介 IEEE 802.11是現今無線區域網通用的標準，它是由國際電機電子工程學會(IEEE)所定義的

django 前後臺互動過程

node2:/tlcb/mysite/mysite#cat urls.py """mysite URL Configuration The `urlpatterns` list routes URLs to views. For more information pl

smtp互動過程

事先宣告，整個過程以LOGIN認證方式為例，其他認證方式大同小異。按照時間順序，主要分為22個步驟。 1、客戶端TCP連線伺服器25埠; 2、三次握手以後，連線建立成功，伺服器主動推送服務就緒資訊 網易郵箱一般都形如“220 163.com Anti-spam GT

Live555原始碼徹底解密(testRTSPClient --rtsp互動流程)

傳送describe： DESCRIBE rtsp://192.168.3.79:8554/h264ESVideoTest RTSP/1.0 CSeq: 2 User-Agent: f:\ffmpeg-encode-decode\流媒體\Live555\live555\li

關於B/S模式的web服務互動過程中的中文亂碼問題淺析

Web服務是服務端和瀏覽器之間的互動，兩者之間因為中文編碼的問題很容易導致亂碼出現。 站在服務端（servlet）角度，亂碼分成兩種接收請求（request）和響應瀏覽器（response）。 有關亂碼的問題主要是下圖中的四個元件之間的引起的。 （1）request請求產

Servlet的互動過程的詳細講解

Web元件的（Servlet/JSP）的互動：            web元件的跳轉。資料共享。 那為什麼Web元件之間為什麼需要跳轉，需要資料共享。 web元件的跳轉方式： 1：請求轉發：（forward）re

庖丁解牛-----Live555原始碼徹底解密(testRTSPClient --rtsp互動流程)

傳送describe： DESCRIBE rtsp://192.168.3.79:8554/h264ESVideoTest RTSP/1.0 CSeq: 2 User-Agent: f:\ffmpeg-encode-decode\流媒體\Live555\live555\l

DHCP協議格式、DHCP服務搭建、DHCP協商互動過程入門學習

相關學習資料 http://www.rfc-editor.org/rfc/rfc2131.txt http://baike.baidu.com/view/7992.htm?fromtitle=DHCP協議&fromid=1989741&type=syn ht

HTTP協議格式和header、互動過程

HTTP協議格式請求例子 Host: www.baidu.com Connection: Keep-Alive Accept-Encoding: gzip User-Agent: okhttp/3.2.0 username=123&pass

裝置樹 --驅動和裝置樹互動過程

在裝置樹中定義的資訊。flash_SY7803:flashlight { compatible = "qcom,leds-gpio-flash"; //匹配引數 status = "okay";

使用AngularJS實現的前後端分離的資料互動過程

一. AngularJS簡介 AngularJS是什麼 AngularJS是一個開源Web應用程式框架。最初是由MISKO Hevery和Adam Abrons於2009年開發，現