More words.

immutant · Sep 1, 2015 · 88adf85 · 88adf85
1 parent 6898760
commit 88adf85
Showing 1 changed file with 16 additions and 5 deletions.
diff --git a/news/2015-09-01-announcing-2-1-0.md b/news/2015-09-01-announcing-2-1-0.md
@@ -7,10 +7,11 @@ tags: [ releases ]
 ---
 
 We just released Immutant 2.1.0! New features include support for
-[EAP], the latest [WildFly] pre-release, and
+[EAP] and the latest [WildFly] pre-release, as well as initial support
+for
 [HTTP/2](http://undertow.io/blog/2015/04/27/An-in-depth-overview-of-HTTP2.html),
-along with better compatibility with [Datomic]. And a few bug fixes,
-docs and small API tweaks. Details below.
+and better compatibility with [Datomic]. Plus a few bug fixes,
+doc improvements, and small API tweaks. Details below.
 
 ## What is Immutant?
 
@@ -28,15 +29,16 @@ in real world applications.
 * Immutant's messaging library can now be used with [Datomic] either
   in or out of container, as explained more fully in this
   [post](/news/2015/08/03/datomic/).
-* channel timeouts
-* disable concurrent job execution (thank contributor)
 * We had always planned for Immutant to work with Red Hat's
   commercially-supported [EAP] product by making it work with WildFly,
   which will form the foundation for EAP 7, expected to be released
   next year. But we had enough EAP 6 subscribers asking to run
   Immutant that it made sense to try and backport it. So we did!
+  See our [EAP guide] for more details.
 * We upgraded our [Undertow] dependency to its latest official
   release, therefore we now support HTTP/2
+* You can now set a timeout for a WebSocket or HTTP stream. See the
+  [async docs] for more details.
 * We now support 4 -- count 'em, FOUR!!! -- major versions of
   Infinispan for `immutant.caching`. Out of container, we bumped
   Immutant's dependency to Infinispan 7, but when run in EAP, version
@@ -49,6 +51,11 @@ in real world applications.
   previous default behavior was to fail with a warning. As a
   convenience, you may now pass in the id as the value of
   `:singleton`, thereby collapsing two arguments into one.
+* By default, if the action of a scheduled job is running when the
+  same job fires again, the two executions happen in parallel. Thanks
+  to [Fabio Bernasconi], you can now [disable this] on a per-job basis,
+  causing subsequent executions to wait for prior executions to
+  finish.
 
 All of these issues and more are linked below.
 
@@ -82,4 +89,8 @@ you can always find us on [#immutant on freenode](/community/) or
 [Quartz]: http://quartz-scheduler.org/
 [Narayana]: http://www.jboss.org/narayana
 [EAP]: https://www.jboss.org/products/eap
+[EAP guide]: /documentation/2.0.1/apidoc/guide-EAP.html
 [Datomic]: http://www.datomic.com/
+[async docs]: /documentation/2.1.0/apidoc/immutant.web.async.html
+[Fabio Bernasconi]: https://github.com/instilled
+[disable this]: /documentation/2.1.0/apidoc/immutant.scheduling.html#var-allow-concurrent-exec.3F