equal
deleted
inserted
replaced
1 Next steps |
1 Next steps |
2 ---------- |
2 ---------- |
|
3 |
|
4 - finish what was started : |
|
5 |
|
6 - bypass publisher. |
|
7 - tighten the error handling and get a well-behaved application |
|
8 - provide sane default policies that match current cubicweb behavior. |
|
9 |
|
10 - identify what can be done without pushing the 'pyramid way' into cubicweb (as |
|
11 a first step for future evolutions). |
|
12 |
3 |
13 |
4 Provide a ctl command |
14 Provide a ctl command |
5 ~~~~~~~~~~~~~~~~~~~~~ |
15 ~~~~~~~~~~~~~~~~~~~~~ |
6 |
16 |
7 Add a 'pyramid' command for cubicweb-ctl that starts a cubicweb instance within |
17 Add a 'pyramid' command for cubicweb-ctl that starts a cubicweb instance within |
11 ~~~~~~~~~~~~ |
21 ~~~~~~~~~~~~ |
12 |
22 |
13 A common transaction handling mechanism should be used so that the connexion |
23 A common transaction handling mechanism should be used so that the connexion |
14 can be safely used in both pyramid and cubicweb. |
24 can be safely used in both pyramid and cubicweb. |
15 |
25 |
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 |
26 Reimplement the base controllers of cw |
34 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
27 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
35 |
28 |
36 - rest |
29 - rest |
37 - static |
30 - static |