Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OM2M/Roadmap"
< OM2M
(Created page with "This page describes the current plan for the upcoming features of the Eclipse OM2M project. Please note that this plan is a moving target - depending on priorities and communi...") |
|||
| Line 3: | Line 3: | ||
== Release 1.0.0 == | == Release 1.0.0 == | ||
| − | The first release of OM2M is planned for March 2015. It includes the following features: | + | The first release of OM2M is planned for 31 March 2015. It includes the following features: |
* Replace the XSD resource validation with a native code to provide flexibility. | * Replace the XSD resource validation with a native code to provide flexibility. | ||
| Line 10: | Line 10: | ||
* Replace the DB4O database with the H2 database which provide better performance. | * Replace the DB4O database with the H2 database which provide better performance. | ||
* Introduce persistence parameters to the "config.ini" file to simplify the JPA configuration. | * Introduce persistence parameters to the "config.ini" file to simplify the JPA configuration. | ||
| − | * Improve the OM2M performance by optimizing database access. | + | * Improve the OM2M performance by optimizing the resource structure and database access. |
| + | * Provide a long-polling mechanism for NAT traversing based on the resource "CommunicationChannel". | ||
| − | + | == Release 2.0.0 == | |
| − | + | ||
| − | + | ||
| − | + | The second release of OM2M is planned for 30 September 2015. It includes the following features: | |
| − | + | * New implementation of OM2M compliant with the new OneM2M standard. For more information about OneM2M see http://www.onem2m.org/ | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 07:57, 1 March 2015
This page describes the current plan for the upcoming features of the Eclipse OM2M project. Please note that this plan is a moving target - depending on priorities and community contribution and commitments, the plan can change any time, so do not take it for granted, but see it as a guidance of direction.
Release 1.0.0
The first release of OM2M is planned for 31 March 2015. It includes the following features:
- Replace the XSD resource validation with a native code to provide flexibility.
- Replace the OASIS OBIX library with a native code based on the JAXB library.
- Provide a persistence solution layer based on EclipseLink JPA library to support various database solutions.
- Replace the DB4O database with the H2 database which provide better performance.
- Introduce persistence parameters to the "config.ini" file to simplify the JPA configuration.
- Improve the OM2M performance by optimizing the resource structure and database access.
- Provide a long-polling mechanism for NAT traversing based on the resource "CommunicationChannel".
Release 2.0.0
The second release of OM2M is planned for 30 September 2015. It includes the following features:
- New implementation of OM2M compliant with the new OneM2M standard. For more information about OneM2M see http://www.onem2m.org/