The execution context of a handler execution.
When Vert.x provides an event to a handler or calls the start or stop methods of a
the execution is associated with a
Usually a context is an event-loop context and is tied to a specific event loop thread. So executions for that context always occur on that exact same event loop thread.
In the case of worker verticles and running inline blocking code a worker context will be associated with the execution which will use a thread from the worker thread pool.
When a handler is set by a thread associated with a specific context, the Vert.x will guarantee that when that handler is executed, that execution will be associated with the same context.
If a handler is set by a thread not associated with a context (i.e. a non Vert.x thread). Then a new context will be created for that handler.
In other words, a context is propagated.
This means that when a verticle is deployed, any handlers it sets will be associated with the same context - the context of the verticle.
This means (in the case of a standard verticle) that the verticle code will always be executed with the exact same thread, so you don't have to worry about multi-threaded acccess to the verticle state and you can code your application as single threaded.
This class also provides runOnContext which allows an action to be executed asynchronously using the same context.
no subtypes hierarchy
|Attributes inherited from: |
If the context is associated with a Verticle deployment, this returns the configuration that was specified when the verticle was deployed.
If the context is associated with a Verticle deployment, this returns the deployment ID of that deployment.
Invoke executeBlocking with order = true.
Safely execute some blocking code.
Executes the blocking code in the handler
When the code is complete the handler
Get some data from the context.
@return the number of instances of the verticle that were deployed in the deployment (if any) related to this context
Is the current context an event loop context?
NOTE! when running blocking code using executeBlocking from a standard (not worker) verticle, the context will still an event loop context and this will return true.
Is the current context a multi-threaded worker context?
Is the current context a worker context?
NOTE! when running blocking code using executeBlocking from a standard (not worker) verticle, the context will still an event loop context and this will return false.
@return The Vertx instance that created the context
The process args
Put some data in the context.
This can be used to share data between different handlers that share a context
Remove some data from the context.
Run the specified action asynchronously on the same context, some time after the current execution has completed.
|Methods inherited from: |