-
Notifications
You must be signed in to change notification settings - Fork 1
/
tasks.txt
65 lines (48 loc) · 2.39 KB
/
tasks.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
NOTES (include bibliography):
- psycopg is a Python DB API compliant library, therefore, when .execute() is called, a "begin transaction;" is called
and awaits for .commit() or .rollback(). in this case, conn.autocommit = True
- all queries, regardless of their atomicity, are encapsulated in a transaction,
Questions:
- psycopg always begins transactions, how not to begin transaction in a SELECT?
- how do we END an auction at the given timestamp? 1) polling process? 2) any request checks if the auction is closed?
R: implement DATE checking in some requests | remove status from table
Decision-making (include bibliography):
- token goes ALWAYS in request params (through link). it's not the best choice because of low security standards, though. anyways, it's very good for testing in the web-browser.
the best choice is using cookies.
why doesnt token go in body-params? well, that would work out in a POST request, but not quite in a GET request. technically it might work, but it stands against HTTP/1.1 standards.
(https://tools.ietf.org/html/rfc2616#section-9.3)
- get requests with input trigger a specific feature in flask. /dbproj/leilao/{keyword} would go as described:
https://stackoverflow.com/questions/19212980/custom-routing-in-flask-app
https://hackersandslackers.com/flask-routes/
- errors outputted by SQL --> we know its not SAFE but it's easier
Tasks:
XM - login
XM - signup
XM - create auction
XR - list all ON auctions
XM - query ON auctions | variant for ALL auctions
XR - query auction details
XR - list all auctions a user has activity // GET dbproj/meusleiloes
XR - bid on an auction // sends notification to previous bidder
XM - edit auction properties (description, title)
XM - write message on an auction // delivers notification to all involving users
XR - list notifications
X - check all functions' behaviour about end_date
X - check auths
X - check transactions
- final docs on each function
Paper:
- user manual with REST API docs
-- think about dividing endpoints by category
-- signal with PUBLIC or PRIVATE (needs auth)
- installation manual
-- basically, README
- final ER and Relational Data Models
-- grab old json and update it (and .sql)
- development plan
-- above tasks & think about others not specified
- final notes on decision-making (above)
- bibliography
- SOURCE CODE dont forget
Presentation:
- 10 min short powerpoint