Tag Archives: Async

ES7 async/await with Aurelia


via ES7 async/await with Aurelia.

In this post we’ll cover how the new Async/await keywords can be used in conjunction with Aurelia’s screen activation lifecycle.

In Aurelia you can opt-in to any of the screen activation lifecycle events by implementing the appropriate method on your viewmodel. If your method returns a promise, the router will wait for the promise to resolve before proceeding to the next step.

JQuery AJAX Example


via jQuery AJAX Example | Web Code Geeks.

The aim of this example is to give you a full understanding of AJAX, which stands for Asynchronous Javascript and XML. Ajax is not a programming language or a tool, but a concept.

Ajax is a client-side script that communicates to and from a server/database without the need for a postback or a complete page refresh.

The best definition for Ajax would be “the method of exchanging data with a server, and updating parts of a web page – without reloading the entire page.”

Ajax itself is mostly a generic term for various JavaScript techniques used to connect to a web server dynamically without necessarily loading multiple pages. In a more narrowly-defined sense, it refers to the use of XmlHttpRequest objects to interact with a web server dynamically via JS.

Announcing Java SDK 2.2 General Availability


via Announcing Java SDK 2.2 General Availability.

On behalf of the SDK Team, it is my great pleasure to announce that the Java SDK version 2.2 is now GA!

This version is packed with enhancements and bugfixes. First and foremost it offers compatibility with all the new shiny things our new Couchbase Server 4.0brings to the table.

Thanks to feedback and after quite a few iterations (there were not one but two Developer Previews for this release!), we now have a rich set of improvements to take advantage of when migrating from 2.0/2.1 to 2.2.

See the release notes for a complete list of changes, but here is a recap:

Lock on asynchronous code for NodeJS


via rain1017/async-lock · GitHub.

Nodejs is single threaded, and the code execution is never get interrupted inside an event loop, so locking is unnecessary? This is true ONLY IF your critical section can be executed inside a single event loop. However, if you have any async code inside your critical section (it can be simply triggered by any I/O operation, or timer), your critical logic will across multiple event loops, therefore it’s not concurrency safe!

Consider the following code

Non-blocking Asynchronous JSON.parse Using The Fetch API


via Non-blocking Asynchronous JSON.parse Using The Fetch API.

I am working on Swagger Editor performance. One of the solutions to speed things up was moving process-intensive task to Web Workers. Web Workers do a great job of moving process-heavy tasks out of the main thread but the way we can communicate with them is very slow. For each message to be sent to or received from a worker we need to convert it to a string. This means for transferring objects between the main thread and worker threads we need to JSON.parse and JSON.stringify our objects back and forth.

How to reduce the load time of a web page with asynchronous CSS


via How to reduce the load time of a web page with asynchronous CSS » OpenAlfa Blog.

We have already stressed in previous posts the importance of the time it takes for a web page to be fully loaded in the client browser: users will get a better impression of the site if the content is “snappy”. Besides, the page load time is a factor that the major search engines, including Google, take into account in their ranking algorithms.

Downloading and processing external resources is often one of the main contributions to the total page load time. Among these resources, external javascript libraries and CSS stylesheets are most often the main contributors to this.

We have already covered in our previous post on “How to reduce the page load time with asynchronous javascript” the way to load javascript resources in parallel with the main HTML document, so as not to block the rendering of the above-the-fold content.

This post continues the series on web site optimization techniques, explaining how to load asynchronously external CSS stylesheets.

Part 1: Service Bus SDK 3.0.x


via Service Bus SDK 3.0.x Part 1 – ServiceBus – Site Home – MSDN Blogs.

Last week we released our new Service Bus SDK for .NET and we want to publish a series of blogs about it addressing the major changes. This may end up being a fairly long series… but we’ll see.

First and foremost was the move away from the Asynchronous Programming Model (APM) pattern. This pattern, which dates from the earliest days of .NET, required Begin and End operations for all asynchronous methods. APM was a very useful model and was fairly easy to work with considering what it enabled. All scalable systems are asynchronous in nature and Service Bus has always supported asynchronous programing. It’s the only way to get really good performance.

The move to the Task-based Asynchronous Pattern (TAP) uses a single method to represent both the initiation and completion of asynchronous operations. TAP, which was introduced in .NET Framework 4 is the recommended approach to asynchronous programming in the .NET Framework. The async and await keywords were added to support TAP within the C# language.

This provides several key advantages; performance and ease of use being the most compelling.