object ExecutorScheduler extends Serializable
- Source
- ExecutorScheduler.scala
- Alphabetic
- By Inheritance
- ExecutorScheduler
- Serializable
- AnyRef
- Any
- Hide All
- Show All
- Public
- Protected
Value Members
- def apply(service: ExecutorService, reporter: UncaughtExceptionReporter, executionModel: ExecutionModel, features: Features): ExecutorScheduler
Builder for an ExecutorScheduler, converting a Java
ScheduledExecutorService.Builder for an ExecutorScheduler, converting a Java
ScheduledExecutorService.- service
is the Java
ScheduledExecutorServicethat will take care of scheduling and execution of all runnables.- reporter
is the UncaughtExceptionReporter that logs uncaught exceptions.
- executionModel
is the preferred ExecutionModel, a guideline for run-loops and producers of data.
- features
is the set of Features that the provided
ExecutorServiceimplements, see the documentation for Scheduler.features
- def forkJoinDynamic(name: String, parallelism: Int, maxThreads: Int, daemonic: Boolean, reporter: UncaughtExceptionReporter, executionModel: ExecutionModel): ExecutorScheduler
Creates an ExecutorScheduler backed by a
ForkJoinPoolintegrated with Scala'sBlockContext. - def forkJoinStatic(name: String, parallelism: Int, daemonic: Boolean, reporter: UncaughtExceptionReporter, executionModel: ExecutionModel): ExecutorScheduler
Creates an ExecutorScheduler backed by a
ForkJoinPoolthat isn't integrated with Scala'sBlockContext.
Deprecated Value Members
- def apply(service: ExecutorService, reporter: UncaughtExceptionReporter, executionModel: ExecutionModel): ExecutorScheduler
DEPRECATED — provided for binary backwards compatibility.
DEPRECATED — provided for binary backwards compatibility.
Use the full-featured builder.
- Annotations
- @deprecated
- Deprecated
(Since version 3.0.0) Use the full-featured builder
This is the API documentation for the Monix library.
Package Overview
monix.execution exposes lower level primitives for dealing with asynchronous execution:
Atomictypes, as alternative tojava.util.concurrent.atomicmonix.catnap exposes pure abstractions built on top of the Cats-Effect type classes:
monix.eval is for dealing with evaluation of results, thus exposing Task and Coeval.
monix.reactive exposes the
Observablepattern:Observableimplementationsmonix.tail exposes Iterant for purely functional pull based streaming:
BatchandBatchCursor, the alternatives to Scala'sIterableandIteratorrespectively that we are using within Iterant's encodingYou can control evaluation with type you choose - be it Task, Coeval, cats.effect.IO or your own as long as you provide correct cats-effect or cats typeclass instance.