[erlang-questions] [ANN] CloudI 1.6.0 Released!

Michael Truog <>
Thu Jan 12 01:40:07 CET 2017


Download 1.6.0 from 
http://sourceforge.net/projects/cloudi/files/latest/download
(checksums at the bottom of this email)

CloudI (http://cloudi.org/) is a "universal integrator" using an Erlang 
core to
provide fault-tolerance with efficiency and scalability.  The CloudI API
provides a minimal interface to communicate among services so programming
language agnostic and protocol agnostic integration can occur.
CloudI currently integrates with the programming languages
C/C++, Elixir, Erlang, Java, JavaScript/node.js, PHP, Perl, Python, and 
Ruby,
while including many reusable services that rely on the CloudI service bus.

The details for this release are below:
   * backwards compatibility difference:
     * Functions deprecated in the 1.3.3 CloudI release have been removed
     * Usage of the 'immediate' atom for the timeout value with the
       cloudi_service Erlang module and the cloudi Erlang module is 
deprecated,
       use the 'limit_min' atom instead for the same value
     * The minimum allowable values for service configuration
       (both adding a new service and updating an existing service) of
       timeout_async and timeout_sync has changed from
       101 milliseconds to 499 milliseconds to be consistent with
       the value that 'limit_min' represents
     * The service configuration options
       request_timeout_immediate_max and response_timeout_immediate_max
       had their meaning change to rely on a greater than or equal to
       comparison instead of a greater than comparison, though the same
       default behavior is preserved with this change
       (http://cloudi.org/api.html#2_services_add_config_opts)
   * Now cloudi_core doesn't use any port drivers or NIFs except what is
     provided within Erlang/OTP, and process dictionary use is minimal
   * The Elixir module CloudILogger is now included in the cloudi_core
     Erlang application to simplify usage of CloudI in Elixir source code
   * Bugs related to CloudI logging syslog integration have been fixed and
     more options for syslog use have been added
     (http://cloudi.org/api.html#2_logging_syslog_set has more information)
   * The restart_delay service configuration option was added
(http://cloudi.org/api.html#2_services_add_config_opts_restart_delay)
   * CloudI service restarts have been made synchronous to ensure all
     termination has completed before initialization of new processes begins
     (to improve reliable management of global state during a restart)
   * All service configuration timeout values that take milliseconds also
     accept the Erlang atoms 'limit_min' and 'limit_max' where 'limit_max'
     is a concept similar to the 'infinity' atom in Erlang source code,
     though it does represent 49.7 days in milliseconds, so be careful about
     its use (no one wants to wait 49.7 days to see a failure)
   * All CloudI API implementations now handle a null return value as a 
response
     to create a null response, if the programming language has a concept of
     null (for more information, see the null integration test
     http://cloudi.org/tutorials.html#cloudi_examples and/or read about
     a null response at http://cloudi.org/faq.html#4_Null)
   * All CloudI API implementations now put stdout and stderr into 
unbuffered
     mode to ensure CloudI service output is logged as quickly as possible
   * Bugs were fixed and other improvements were added
     (see the ChangeLog for more detail)

Please mention any problems, issues, or ideas!
Thanks,
Michael

SHA256 CHECKSUMS
cloudi-1.6.0.tar.gz (14363598 bytes)
4f14f508a2a4840026faf38c8abd7b13f314c619a8bafd59703cf59b1dd864a1
cloudi-1.6.0.tar.bz2 (12330051 bytes)
1045cceb890fa7310c80aa6e783c5b480e1700346ff6d26cac67dbbd35704518



More information about the erlang-questions mailing list