[jira] [Updated] (UIMA-18) Placeholder for Architectural Cleanups / Changes

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor updated UIMA-18:
-------------------------------
    Description: 
This is a place to list architectural cleanup issues.  Edit this to fix / augment.  Perhaps sub-tasks of this can be particular issues we decide are being worked on.

1) Index for everything (needed for simple access to singletons)
* 2016 status: have auto default bag index for everything

2) Simple access for singletons
* 2016 status: there's an add-on for this

3) Deciding about Sofa names and View names, (not)having a 1-1 correspondence between sofas and views.
* 2016 status: sofa names and view names are treated as the same in the current design, so there's a required 1-1 correspondence between sofas and views.

4) Removing/reducing type system augmentation via merging
* 2016 status: type system merging a core part.

5) Begin able to configure remote components
* 2016 status: no support for this. Remote components (e.g. services) configured when they start up.  Any "parameters" that need to be passed from client to server need to be passed in the individual CAS being sent, as part of the user's design.

6) Adding "session" caching for remote components
* 2016 status: not done, not contemplated

7) Supporting operations over sets of multiple CASes with more than just external resources

8) Integrating OSGi enablement

  was:
This is a place to list architectural cleanup issues.  Edit this to fix / augment.  Perhaps sub-tasks of this can be particular issues we decide are being worked on.

1) Index for everything (needed for simple access to singletons)

2) Simple access for singletons

3) Deciding about Sofa names and View names, (not)having a 1-1 correspondence between sofas and views.

4) Removing/reducing type system augmentation via merging

5) Begin able to configure remote components

6) Adding "session" caching for remote components

7) Supporting operations over sets of multiple CASes with more than just external resources

8) Integrating OSGi enablement


> Placeholder for Architectural Cleanups / Changes
> ------------------------------------------------
>
>                 Key: UIMA-18
>                 URL: https://issues.apache.org/jira/browse/UIMA-18
>             Project: UIMA
>          Issue Type: Improvement
>            Reporter: Marshall Schor
>            Priority: Minor
>
> This is a place to list architectural cleanup issues.  Edit this to fix / augment.  Perhaps sub-tasks of this can be particular issues we decide are being worked on.
> 1) Index for everything (needed for simple access to singletons)
> * 2016 status: have auto default bag index for everything
> 2) Simple access for singletons
> * 2016 status: there's an add-on for this
> 3) Deciding about Sofa names and View names, (not)having a 1-1 correspondence between sofas and views.
> * 2016 status: sofa names and view names are treated as the same in the current design, so there's a required 1-1 correspondence between sofas and views.
> 4) Removing/reducing type system augmentation via merging
> * 2016 status: type system merging a core part.
> 5) Begin able to configure remote components
> * 2016 status: no support for this. Remote components (e.g. services) configured when they start up.  Any "parameters" that need to be passed from client to server need to be passed in the individual CAS being sent, as part of the user's design.
> 6) Adding "session" caching for remote components
> * 2016 status: not done, not contemplated
> 7) Supporting operations over sets of multiple CASes with more than just external resources
> 8) Integrating OSGi enablement



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)