Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
02/15/11 11:12:16 (13 years ago)
- Author:
-
wmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Sprint
changed from
2011-02-10 (5)
to
2011-02-24 (6)
-
|
initial
|
v4
|
|
| 20 | 20 | - API? |
| 21 | 21 | |
| 22 | | == API Unification: points to consider == |
| 23 | | - Who are our API consumers? |
| 24 | | - Will devs move from Python API to Java etc, or just use their favorite language only? |
| 25 | | - 'Behavior' differences. |
| 26 | | - Number of server calls ('Lazy' loading vv loading graph) |
| 27 | | - Is the Blitz gateway suitable as a general purpose Python API (scripting service, 'remote' Python clients etc) |
| | 22 | == Current Strategy, based on first meeting (notes below) == |
| | 23 | - Goal is to move as much logic as possible server-side |
| | 24 | - All API methods should be moved (eventually) to a single "New Gateway" service (need new name!). Need to decide how to handle stateful services. |
| | 25 | - This service will have all language-agnostic logic. |
| | 26 | - Language-specific convenience methods should be elsewhere E.g. getPlane() returns 2D numpy array etc. in wrapper objects. |
| | 27 | - Mark services/methods as "deprecated" where possible in 4.3, using Ice, Python, Java conventions. getGateway() service is a priority. |
| | 28 | - Move the frequently used script_utils functionality into blitz gateway. |
| | 29 | - Continue to clean up blitz gateway API, with matching methods in "New Gateway" where possible (language agnostic and stateless) |
| | 30 | |
| | 31 | |
| 28 | 32 | |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.16041 sec.)
