2012-09-11 09:16:17 +02:00
|
|
|
.. _experimental:
|
|
|
|
|
|
|
|
|
|
####################
|
|
|
|
|
Experimental Modules
|
|
|
|
|
####################
|
|
|
|
|
|
|
|
|
|
The following modules of Akka are marked as experimental, which means
|
2012-09-11 15:22:17 +02:00
|
|
|
that they are in early access mode, which also means that they are not
|
|
|
|
|
covered by commercial support. The purpose of releasing them early, as
|
|
|
|
|
experimental, is to make them easily available and improve based on
|
|
|
|
|
feedback, or even discover that the module wasn't useful.
|
2012-09-11 09:16:17 +02:00
|
|
|
|
|
|
|
|
An experimental module doesn't have to obey the rule of staying binary
|
|
|
|
|
compatible between minor releases. Breaking API changes may be introduced
|
|
|
|
|
in minor releases without notice as we refine and simplify based on your
|
|
|
|
|
feedback. An experimental module may be dropped in major releases without
|
|
|
|
|
prior deprecation.
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
2012-09-22 09:21:21 +02:00
|
|
|
:maxdepth: 1
|
2012-09-11 09:16:17 +02:00
|
|
|
|
|
|
|
|
../cluster/index
|
2012-09-20 21:50:35 +02:00
|
|
|
../dev/multi-node-testing
|
2012-09-27 15:57:46 +02:00
|
|
|
|
|
|
|
|
Another reason for marking a module as experimental is that it's too early
|
|
|
|
|
to tell if the module has a maintainer that can take the responsibility
|
|
|
|
|
of the module over time. These modules live in the ``akka-contrib`` subproject:
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
|
|
|
|
../b/../../../akka-contrib/docs/index.rst
|
|
|
|
|
|
