forked from CoderLisa/gdeproxy
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTODO
22 lines (18 loc) · 761 Bytes
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
super-easy assertions on message chains, handlings, requests, and responses - for use by importers
extract classes for handling http version 0.9, 1.0, and 1.1
extract client connector -> Conforming vs. Bare
extract server connector -> Conforming vs. Bare
add endpoint parameter to handler functions, so we know who handled the request ?
no use-case for this yet
chunked body reading
binary body
compression
clean endpoint failure, e.g. if address already in use
shouldn't get added to _endpoints list
thread(s) should be shut down
option on route to be transparent or not (see http rfc) ?
route should use the conforming client connector above
not sure which server connector to use
server-side https
test https
test route https