User Cookie
This is needed to make #32 effective and will be essential for a conversational interface
- A new property for the Query object:
userId
(this is (as wanted) automatically then used in caching) - A new member for the Query object to store cookies
- If not present in the request, an ID String is randomly generated and send to the client through this:
Set-Cookie: user=<random>; Domain=args.me; SameSite=Lax
- If present in the request, the Query property will be set and the cookie stored. The stored cookie will be played back to the client on response
- In the future, there will be a page that allows to add
Max-Age=<seconds>
to the cookie, thereby making the cookie last longer than a session. This should also be played back on response (might need adjustments?)
Desirable:
- Is it possible to not create a cookie (unless it exists) when querying the API?