-
Notifications
You must be signed in to change notification settings - Fork 402
Comments
Conversation
WARNING: This is work in progress, expect rebasing and force-pushes! Feedback is very welcome!
This pull request adds the ability to distribute compiled or uncompiled erlang modules to all nodes. The goal is to significantly simplify the usage of custom code/modules especially in a distributed setup to be used in sessions e.g. via
The proposed option to specify modules is the following:
<option name="module_distribution" module_type="beam" value="my_module" />
<option name="module_distribution" module_type="source" value="/tmp/my_modules/my_utils.erl" />
options>
Module type beam will be loaded, so they have to be on the controllers load path (see command line option -X added in #92). Modules of type source are compiled via compile:file(Path, [binary, compressed, return]). Compilation errors and warnings will be logged, where compilation errors will result in tsung termination.
Any module is distributed to all nodes, including remote beams, via rpc:multicall(Nodes, code, load_binary, [Module, Filename, Binary], ?RPC_TIMEOUT) so that they are usable right away.
|
@nniclausse thanks for the hint. I think I'm also missing several spots, where new beams are launched. |
fix typos
update vsn to dev branch
more verbose store/restore parsing
update mailmap
correct debian compatibility level
correct debian compatibility level, cf debhelper
increase doc version
new release
remove unused file (we use builtin eldap)
fix for new websocket api: needs origin argument
fix changelog name
v1.7.0
update doc and changelog
small update to changelog
fix url
preparing release
add travis badge in readme
remove old erlang versions from travis
add erlang test version
add entries in changelog for next release
...