You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggested by Mark Mandel--would be nice to be able to specify the total number of threads that are used by Mach-II's pub/sub listener notifications so the asynchronous threads don't hog up all the CFML engine threads.
Another idea might be to allow for specifying the message block as asynchronous, but then specify that subscribers are or are not threaded.
Changed 2 years ago by peterfarrell
Priority changed from blocker to minor
Version changed from 1.9.0 - Framework to Uncategorized - Framework
Milestone changed from Mach-II 1.9.0 alpha to Uncategorized
Might be useful but not real world use case yet.
The text was updated successfully, but these errors were encountered:
(Moved from http://trac.mach-ii.com/machii/ticket/266)
Suggested by Mark Mandel--would be nice to be able to specify the total number of threads that are used by Mach-II's pub/sub listener notifications so the asynchronous threads don't hog up all the CFML engine threads.
Another idea might be to allow for specifying the message block as asynchronous, but then specify that subscribers are or are not threaded.
Changed 2 years ago by peterfarrell
Priority changed from blocker to minor
Version changed from 1.9.0 - Framework to Uncategorized - Framework
Milestone changed from Mach-II 1.9.0 alpha to Uncategorized
Might be useful but not real world use case yet.
The text was updated successfully, but these errors were encountered: