-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.TODO
executable file
·126 lines (100 loc) · 4.92 KB
/
README.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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
Full spec can be found here:
http://extjs.com/products/extjs/direct.php
======================================================================
OPTIONAL FEATURES - from Specification
======================================================================
Most of these notes refer to the modperl/ implementation.
Remoting methods by metadata - Custom annotations and attributes
----------------------------------------------------------------------
STATUS: Not started - some form of introspection, or using Moose
See Introspection below
Programmatic, JSON or XML configuration
----------------------------------------------------------------------
STATUS: Complete
Type conversion
----------------------------------------------------------------------
STATUS: Not started - consider some automation, e.g. Date formats
Asynchronous method calls
----------------------------------------------------------------------
STATUS: Not started - consider threads, callbacks, Aysnc and POE.
Method batching
----------------------------------------------------------------------
STATUS: Complete - Built in requirement
File uploading
----------------------------------------------------------------------
STATUS: WIP
Specify before and after actions to execute allowing for aspect
oriented programming. This is a powerful concept which can be used
for many uses such as security.
----------------------------------------------------------------------
STATUS: Complete
pre and post methods on action and each method
Basic function to load 'before' and 'after' code on the action and
the individual methods. NOTE: Currently, to implement security check
you would need to do a 'die' to stop the process. See Debugging.
NOTE: Consider updating to use 'Hook'=> {before=>...} instead.
======================================================================
OPTIONAL FEATURES - from Scott
======================================================================
Apache access controls
----------------------------------------------------------------------
STATUS: WIP (just user and group methods)
Use basic Apache style user/group (valid-user or list) for access.
This can be done with the before method, but it is nicer to be build in.
Data integrity checking
----------------------------------------------------------------------
STATUS: Not started
Ability to check what type of values we have received before
executing the main method
Data security checking
----------------------------------------------------------------------
STATUS: Not started
Checking valid data inputs, like removal of NULL and script tags.
Testing and changes to allow module to work in taint mode.
Pre-loading Classes at Startup
----------------------------------------------------------------------
STATUS: Complete
Used with an Apache handler, all classes and instantiations can be done
at Apache start time, before any further forks. It can also be done
post fork, in case instantiations need database or similar.
(NOTE: Just use Apache::DBI for DB caching, but be aware of SQLite locks)
Instantiation
----------------------------------------------------------------------
STATUS: Complete
Each Perl class that is associated with an action can be used as a
class with class methods, or instantiated as an object (optional
parameters can be passed in via configuration - anything more complicated
would need to be done by wrapper method) and call those object methods.
Debugging
----------------------------------------------------------------------
STATUS: Not started
Ability to turn on debugging to pass back further information to Ext
in JSON readable format.
Full revamp of reporting and logging too.
How to report normal faiulres, like a 'before' action failing, or
the access control limits. Need to consider standard JSON return data.
See Ext internals for possible return values, similar to the debugging.
Alternative class
----------------------------------------------------------------------
STATUS: Complete
The actual class loaded for each "action" is defined in the configuraiton.
Alternative methods
----------------------------------------------------------------------
STATUS: Not started
It may be desirable to change the method called.
E.g. an existing interface may use a legal javscript method name that
is not legal in perl.
======================================================================
IMPORTANT IMPROVEMENTS
======================================================================
This lists important improvements that need to be made
Configuration checks
----------------------------------------------------------------------
STATUS: Not started
The system currently depends on a well formatted configuration file.
But this is not checked at startup / read time.
======================================================================
BUGS
======================================================================
Outstanding bugs - remove when fixed.
* post_config/child_init not able to read configuration data !