equal
deleted
inserted
replaced
|
1 Next steps |
|
2 ---------- |
|
3 |
|
4 Provide a ctl command |
|
5 ~~~~~~~~~~~~~~~~~~~~~ |
|
6 |
|
7 Add a 'pyramid' command for cubicweb-ctl that starts a cubicweb instance within |
|
8 a pyramid container. |
|
9 |
|
10 Transactions |
|
11 ~~~~~~~~~~~~ |
|
12 |
|
13 A common transaction handling mechanism should be used so that the connexion |
|
14 can be safely used in both pyramid and cubicweb. |
|
15 |
|
16 Authentication |
|
17 ~~~~~~~~~~~~~~ |
|
18 |
|
19 - Use cw as an authentication provider for the pyramid application. |
|
20 - allow the cw application to use pyramid for getting user identity. |
|
21 |
|
22 Cubicweb views |
|
23 ~~~~~~~~~~~~~~ |
|
24 |
|
25 Provide a simple api to call cubicweb views within pyramid views. |
|
26 |
|
27 Error handling |
|
28 ~~~~~~~~~~~~~~ |
|
29 |
|
30 Have pyramid handle errors (with cubicweb views if wanted) so that we can use |
|
31 the debuging tools. |
|
32 |
|
33 Reimplement the base controllers of cw |
|
34 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
35 |
|
36 - rest |
|
37 - static |
|
38 - data |
|
39 |
|
40 Bypass cw.handle_request in most case |
|
41 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
42 |
|
43 Use it only when no other mean works, which should provide backward compat of |
|
44 old cubes for a while. |