forked from hyperglyph/hyperglyph
/
todo
104 lines (77 loc) · 2.19 KB
/
todo
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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
next commits:
python:
relative url handling (+tests for url less forms in resources)
new encoder/decoder w/ dependencies & resolver / constructors
maybe py2/
error mapping
client error /server error
handle unknown content types as blob
method names in method not in url mapping
handled, but not used.
http 1.1 server
refactor?
glyph.client, glyph, resource, server
py.test over unittest
blob support for returns, etc
client/server if allow="*"
ruby:
done: avoid to_sym
form input support
somewhat: no names or default value support
better ordered dictionaries
done
relative url handling
error mapping
spec:
done: allow ordered dicts in places, including form args/data
rejected: flesh out collection type - add useful methods?
speculative commits:
session handler injected into forms rather than being global
can pass in a 'null' session handler, that serializes,
deserializes & fetches by calling directly.
glyph from scratch?
implement everything by spec
perhaps? class instead of builder for router
simplify mapper code, less flexible.
caching/wsgiserver
hack: revision numbers in content-type until stable.
encoding:
see encoding.rst
add data-url/mime blobs
exceptions:
mapping exceptions inside the mapper to error codes
throwing an exception returns that error code
with an 'error' type (similar to 'resource')
caching
caching headers added to responses
@cache(max_age=....)
change url schema to avoid ?
expires information in resource/embed
Glyph.refresh?
forms/links
type args? default values? schema
i expect a thing with these values
url templates for forms with GET method
classes/resources
use a different encoding for them?
rather than possible subelements, they have a url
children is a dict?
remove all instance vars from dict?
have to expose it through @embed?
pagination
http semantics:
support HEAD, OPTIONS?
html serialization
javascript
json for query args perhaps?
or form values
rewrite for python:
class mapper only needs root element, rest are ephemeral?
ports
node.js
objective-c
erlang/riak
jquery plugin?
different transports
udp, openpgm, 0mq?
coap over datagram, http over streams