[
https://issues.jboss.org/browse/CDI-31?page=com.atlassian.jira.plugin.sys...
]
Jonathan Fisher commented on CDI-31:
------------------------------------
I've used the @Asynchronous workaround, which is why I began advocating this position.
While it works ok for small numbers of EJBs, but EJBs aren't nearly as memory
efficient as the pojo based model of CDI.
I'm advocating this position because we all know how long Java specs live for, and
asynchronous dispatching and easy multithreading are going to be huge measurements of
languages in the very near future. While CPU speeds will still increase going into the
future, we're going to see a greater increase in core count and thread count per
core.
Asynchronous events
-------------------
Key: CDI-31
URL:
https://issues.jboss.org/browse/CDI-31
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Events
Affects Versions: 1.0
Reporter: Nicklas Karlsson
Fix For: TBD
Consider including asynchronous events as their were specified in one of the previous
drafts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira