forked from Pylons/pyramid_rpc
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGES.txt
224 lines (146 loc) · 5.33 KB
/
CHANGES.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
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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
unreleased
==========
- Drop Python 3.2 support.
- Add Python 3.5 support.
- AMF
+ Restore compatibility with later releases of PyAMF.
See https://github.com/Pylons/pyramid_rpc/pull/43
0.7.2 (2015-11-17)
==================
- JSON-RPC
+ Fix a bug in batched requests where the Content-Length header was being
copied to the subrequests, causing broken expectations as we were
re-serializing the body with a larger length than the original request.
See https://github.com/Pylons/pyramid_rpc/pull/41
0.7.1 (2015-09-14)
==================
- JSON-RPC
+ Fix a bug in request handling that could occur if an unknown method was
requested. It was generating an internal error instead of a notfound-like
response. See https://github.com/Pylons/pyramid_rpc/pull/40
0.7 (2015-08-11)
================
- XML-RPC
+ Add support for overriding the renderer with extra options via the
new ``renderer`` option on ``add_xmlrpc_method`` and the
``default_renderer`` option on ``add_xmlrpc_endpoint``.
0.6.1 (2015-05-15)
==================
- Releasing is hard, and I missed it up. So now we have 0.6.1 with no
changes from 0.6.
0.6 (2015-05-15)
================
- Pyramid version compatibility
+ pyramid_rpc now requires Pyramid >= 1.4. (Version 0.5.3 will run on
Pyramid >= 1.2, but will not run on Pyramid 1.1.x despite what
setup.py indicates.)
+ Removed pre-1.4 backwards compatibility for custom predicates.
- Tox configuration
+ Added Tox environments checking against older Pyramid versions.
- JSON-RPC
+ Added support for batched JSON-RPC requests (on POST requests only)
See https://github.com/Pylons/pyramid_rpc/pull/35
0.5.3 (2015-05-14)
==================
- XML-RPC, JSON-RPC
+ Fix deprecation warnings on versions of Pyramid >= 1.4 due to the
usage of custom predicates.
0.5.2 (2013-10-01)
==================
Features
--------
- XML-RPC
+ Add support for ``_depth`` argument to
:func:`pyramid_rpc.xmlrpc.xmlrpc_method` to allow it to be used from
within another decorator.
- JSON-RPC
+ Add support for ``_depth`` argument to
:func:`pyramid_rpc.jsonrpc.jsonrpc_method` to allow it to be used from
within another decorator.
0.5.1 (2012-11-25)
==================
Bug Fixes
---------
- XML-RPC
+ Fix an issue generating responses containing non-ascii characters.
0.5 (2012-11-08)
================
Features
--------
- JSON-RPC
+ Added support for JSON-RPC requests over HTTP GET. All version 2.0
parameters are required, but should be embedded in the query string.
+ The ``renderer`` can now be overridden. This will allow
any renderer to be used to convert a method's results to a
JSON-encoded string. Pyramid 1.4+ has a very flexible JSON
renderer that will allow a custom serializer and adapters for
custom data types (see :class:`pyramid.renderers.JSON` for more).
+ Endpoints support ``default_mapper`` and ``default_renderer`` which
are propagated to all methods attached to the endpoint. Individual
methods can override these values if necessary on a case-by-case basis.
- XML-RPC
+ Endpoints support ``default_mapper`` which is propagated to all methods
attached to the endpoint. Individual methods can override this
values if necessary on a case-by-case basis.
Backwards Incompatibilities
---------------------------
- JSON-RPC
+ With HTTP GET support added, any existing installation will now allow
JSON-RPC requests over GET. To disable this, add
``request_method='POST'`` to your endpoint.
+ Notification requests (``id == null``) used to return a
HTTP ``204 No Content`` response. Now they return ``200 OK`` like
everything else, with an empty response.
0.4.1 (2012-10-27)
==================
Features
--------
- Python 3 compatibility.
+ PyAMF is not Python 3 compatible, only JSON-RPC and XML-RPC are
supported for now.
- JSON-RPC
+ The ``data`` attribute of :class:`pyramid_rpc.jsonrpc.JsonRpcError` is
now encoded into the error response.
Backwards Incompatibilities
---------------------------
- JSON-RPC
+ The default exception views are now registered with
:data:`pyramid.security.NO_PERMISSION_REQUIRED` to ensure they are
always invoked.
- XML-RPC
+ Removed deprecated xmlrpc_view API.
+ The default exception views are now registered with
:data:`pyramid.security.NO_PERMISSION_REQUIRED` to ensure they are
always invoked.
0.3.1 (2011-12-12)
==================
Features
--------
- JSON-RPC
+ Added support for named parameters.
0.3 (2011-08-30)
================
Features
--------
- XML-RPC
+ Deprecated the xmlrpc_view API in favor of a new API that
supports more features expected from routes and views including
the ability to set permissions on RPC methods, perform traversal,
and a default view mapper.
- JSON-RPC
+ Removed the *unreleased* JSON-RPC support that was in master.
+ Added a new API for JSON-RPC that supports more features expected
from routes and views including the ability to set permissions on
RPC methods, perform traversal, and a default view mapper.
- Pyramid 1.1+ compatibility.
0.2 (2011-02-26)
================
Features
--------
- AMF support via a PyramidGateway that implements a Pyramid view gateway
for PyAMF.
0.1 (2010-11-09)
================
Features
--------
- XML-RPC support with xmlrpc_view decorator and xmlrpc_endpoint.