\r\n

51Degrees API Documentation  4.4

Search

Documentation

• Features
• Asynchronous Execution

Asynchronous Execution

Introduction

In the context of the Pipeline, asynchronous execution refers to the use of non-blocking processing. Lazy loading is closely related to this as it is effectively non-blocking processing for an individual aspect engine. In contrast, asynchronous execution refers to non-blocking execution of the Pipeline as a whole.

Language support

C# Java PHP Node.js

Select a language to view details of asynchronous execution support for that language.

.NET supports asynchronous code using the Task asynchronous programming model. However, for .NET we have decided to implement a lazy loading feature instead of a fully asynchronous approach as we believe this gives better control to the developer.

Java supports asynchronous code using the CompletableFuture class. For Java we have decided to implement a lazy loading feature instead of a fully asynchronous approach as we believe this gives better control to the developer.

PHP is single-threaded and does not support non-blocking execution out of the box. The Pipeline has no support for asynchronous execution nor lazy loading in PHP.

Node.js, being based on JavaScript is a fundamentally asynchronous language. As such, the Pipeline will work in a non-blocking way by default through the use of promises.

See the node documentation for more details about blocking vs non-blocking calls.

Generated by doxygen 1.8.15