AsEco does pretty much the same thing that ECO templates templates do, with the following delicate differences:
Streaming: Rather than rendering the template completely into a buffer first, and then outputting that buffer to the client, AsEco templates output chunks of their content directly and immediately into the output stream as soon as that makes sense.
Asynchronous: AsEco support calling asynchronous methods from within the template, i.e. methods that don't do anything at the time, but return their result at a later time using a callback function. AsEco templates understand this paradigm and pause the output stream at this point until the callback method gets called. The rendering continues normally after that.
Working examples are given in the example directory.
Here is an example CoffeeScript file that renders a template.
# Load the required libraries.AsyncFuture = require 'async_future.coffee'AsEco = require 'as_eco'# Simulate slow database operations.=setTimeout -> done_callbackresultdelayuser_loader = simulate_delay1000'John Doe 'city_loader = simulate_delay2000'Los Angeles'# The name of the template file to render.template_filename = './template.as_eco'# The data that should be rendered into the template.data = user: user_loadercity: city_loader# The template writes output by calling this function.out_stream = consolelog# The template calls this function when it is done rendering.= -> consolelog '\n\n[rending finished]'consolelog '[rendering start]\n'AsEcorender_file template_filenamedataconsolelogdone_callback
Here is the corresponding template.
This part is sent immediately.<% async @user.get, user %>This part is sent as soon as the server receives the user information from its backend.<%= user %>While we wait for the city data to become available,we can use CoffeeScript to define and massage data.<% a = 1 %><%= a %><% async @city.get, city %>This part is sent after the expensive backend operation to retrieve city data finishes.<%= city %>