Saxon
401376c059
protocol/rtsp: expected CSeq key is just Cseq now to match ReadResponse result.
2019-04-30 02:19:34 +09:30
Saxon
c552238da5
protocol/rtsp: added some commenting to TestReadResponse and required helper function
2019-04-29 20:18:07 +09:30
Saxon
86bf4cdb90
protocol/rtsp: TestReadResponse now working
2019-04-29 19:28:18 +09:30
Saxon
d2b76fab36
protocol/rtsp: wrote test ReadResponse, but work in progress
2019-04-29 18:21:59 +09:30
Saxon
0a27395aea
protocol/rtsp: doing length check in same if but before RTSP protocol check
2019-04-29 13:35:58 +09:30
Saxon
64f6a3d814
protocol/rtsp: used utter/dump to get ASCII text as well
2019-04-29 13:34:09 +09:30
Saxon
eac5652f1b
protocol/rtsp: in ReadResponse response length check comes before protocol check
2019-04-29 13:19:32 +09:30
Saxon
ba7e768269
protocol/rtsp/cmd/record: sess => clt in record
2019-04-29 13:16:15 +09:30
Saxon
dd58851e6c
protocol/rtsp: added todo to test client connect retry regarding use of generalised retry utility when available.
2019-04-29 13:13:12 +09:30
Saxon
a783b2052e
protocol/rtsp: for test, read buf size is now const called max reequest size
2019-04-29 13:11:27 +09:30
Saxon
66bc6bbe33
protocol/rtsp: only giving Sscanf s[5:] and then checking number of decimals read as well as error
2019-04-29 13:08:05 +09:30
Saxon
77e5d234de
protocol/rtsp: doing RTSP and response length check in same if
2019-04-29 13:03:39 +09:30
Saxon
ba5a0d898c
protocol/rtsp: removed status
2019-04-29 13:01:17 +09:30
Saxon
6605ee7295
protocol/rtsp: general naming clean up
2019-04-29 12:39:58 +09:30
Saxon
d91995a1cf
protocol/rtsp: using bufio.Scanner
2019-04-28 14:04:45 +09:30
Saxon
d7c2421146
protocol/rtsp: fixed sscanf in ReadResponse
2019-04-28 13:51:25 +09:30
Saxon
fa7c3044f3
protocol/rtsp: simplified ReadResponse further by using only one sscanf
2019-04-28 13:23:35 +09:30
Saxon
9abcfb138b
protocol/rtsp: checking error from scans
2019-04-28 12:27:54 +09:30
Saxon
39d0b5d6da
protocol/rtsp: using sscanf to parse response
2019-04-28 02:35:13 +09:30
Saxon
26d05d1bd4
protocol/rtsp/cmd/record: removed stream binary
2019-04-28 01:44:33 +09:30
Saxon
a57d3f66ff
protocol/rtsp: using int rather than int64 for Response.ConentLength
2019-04-28 01:32:44 +09:30
Saxon
94660e730b
protocol/rtsp: using strings.Builder to write String formats for Request and Response
2019-04-28 01:29:47 +09:30
Saxon
eb6b5a04b0
protocol/rtsp: indicate that minResponse size is in bytes
2019-04-28 00:58:33 +09:30
Saxon
31508f8940
protocol/rtsp: removed pre-existing license
2019-04-28 00:57:40 +09:30
Saxon
a62adca171
protocol/rtsp/cmd: renamed stream to record
2019-04-28 00:56:44 +09:30
Saxon
01a22ffc38
protocol/rtsp: Client.Do r parameter now req.
2019-04-28 00:54:44 +09:30
Saxon
07e7235dc4
protocol/rtsp: using string literals for request methods
2019-04-28 00:53:47 +09:30
Saxon
2f752d5b7f
protocol/rtsp: NewClient u parameter now addr and client instance not s now c
2019-04-28 00:51:06 +09:30
Saxon
77094acc67
protocol/rtsp: Client.session => Client.sessionID
2019-04-26 19:53:08 +09:30
Saxon
f2b941394b
protocol/rtsp: fixed read response bug
2019-04-26 19:51:00 +09:30
Saxon
999eab21ab
protocol/rtsp: cleaned up ReadResponse
2019-04-26 19:46:03 +09:30
Saxon
3e17016390
protocol/rtsp: updated licensing
2019-04-26 16:01:57 +09:30
Saxon
f0a1a866dd
protocol/rtsp: removed writeRequest receiver method
2019-04-26 15:09:59 +09:30
Saxon
4998d8d4d6
protocol/rtsp/cmd/stream: using NewClient rather than NewSession
2019-04-26 14:35:25 +09:30
Saxon
14cb6f7f07
protocol/rtsp: reflect go net.http package patterns
...
Request now has a Write receiver method that will write to the passed io.Writer. Client now has Do method that will send the request and return the respons and any errors. Also Renamed the Client
field to Session, which was mistakenly changed.
2019-04-26 14:20:58 +09:30
Saxon
4e98b4d2ea
protocol/rtsp: renamed urlStr to addr
2019-04-26 14:08:58 +09:30
Saxon
cd18d9f5a7
protocol/rtsp: removed Client field from client struct as not useful
2019-04-26 14:07:29 +09:30
Saxon
a0fb299b06
protocol/rtsp: moved client functionality into client.go file
2019-04-26 13:57:18 +09:30
Saxon
9169afe34f
protocol/rtsp: general clean up
2019-04-25 15:30:28 +09:30
Saxon
f3f3be5fc6
protocol/rtsp: completed test for rtsp
...
Completed test to check that each method we support works and can produce valid requests. The requests are compared to requests that have been proven valid. This test also checks that the RTSP
client communicates over tcp correctly. i.e. we have set up a client and server, and we check that this communication happens correctly.
2019-04-25 14:46:21 +09:30
Saxon
adbb9d1c99
protocol/rtsp: added testing file and wrote some signature for possible tests
2019-04-23 17:27:37 +09:30
Saxon
a256dc9133
protocol/rtsp: made rtsp/cmd/stream functional
2019-04-23 16:22:58 +09:30
Saxon
34c59c95d6
protocol/rtsp: working on main.go in rtsp/cmd/stream
...
Added file header to main.go, and modified rtsp.go to work with cmd/stream/main.go. This change modifies writeRequest, which now takes a *url.URL. This means the Setup() method can parse a new
URL that contains a given track, and then give this to writeRequest.
2019-04-23 15:49:54 +09:30
Saxon
d03ae3ff7e
protocol/rtsp: fixed rtsp.go file header indentation
2019-04-23 15:33:07 +09:30
Saxon
68b996f698
protocol/rtsp: removed LICENSE.BSD file as license now in rtsp.go
2019-04-18 13:53:02 +09:30
Saxon
e87eadf8fd
protocol/rtsp/rtsp.go: commenting and general clean up.
2019-04-17 18:31:03 +09:30
Saxon
c9082c1b4c
protocol/rtsp/rtsp.go: put tcp dial in new session
...
tcp dial is now in new session, firstly so that we don't have to do the s.conn == nil check and also so that we dont't have to pass around the url everywhere.
2019-04-17 12:45:02 +09:30
Saxon
85bb88c325
protocol/rtsp: removed README
2019-04-17 12:22:54 +09:30
Saxon
1bcf05830d
protocol/rtsp: removing rtp package
...
We already have an rtp package, which I will extend with client functionality, so we don't need this here.
2019-04-17 12:20:36 +09:30
Saxon
02c11c234f
protocol/rtsp/rtsp.go: added back beatgammits structs
...
Added them back because i realised I can't use http Requests and Responses and the accompanying methods because then this wouldn't be the RTSP protocol, it would be the HTTP protocol, which is not what we're doing.
2019-04-17 12:18:23 +09:30