From 52d7457f1ceb00126b22f9b3ec023f834db0f22d Mon Sep 17 00:00:00 2001
From: Patrick Steele-Idem <pnidem@gmail.com>
Date: Wed, 18 Jun 2014 21:35:11 -0600
Subject: [PATCH] Added support for rendering to an existing stream

---
 README.md                           | 23 ++++++++++++++++++-----
 runtime/raptor-templates-runtime.js |  2 +-
 2 files changed, 19 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index c7401ff8b..d8fe90173 100644
--- a/README.md
+++ b/README.md
@@ -237,6 +237,7 @@ template.render({
 ```
 
 ### Streaming API
+
 ```javascript
 var template = require('raptor-templates').load('template.rhtml');
 var out = require('fs').createWriteStream('index.html', 'utf8');
@@ -249,6 +250,19 @@ template.stream({
     .pipe(out);
 ```
 
+Alternatively, you can render directly to an existing stream to avoid creating an intermediate stream:
+
+```javascript
+var template = require('raptor-templates').load('template.rhtml');
+var out = require('fs').createWriteStream('index.html', 'utf8');
+
+// Render the template to 'index.html'
+template.render({
+        name: 'Frank',
+        count: 30
+    }, out);
+```
+_NOTE:_ This will end the target output stream.
 
 ### Asynchronous Render Context API
 
@@ -1271,23 +1285,22 @@ __Answer__: The runtime for template rendering is supported in all web browsers.
 
 __Question:__ _How can Raptor Templates be used with Express?_
 
-__Answer__: The recommended way to use Raptor Templates with Express is to bypass the Express view engine and instead directly pipe the rendering output stream to the response stream as shown in the following code:
+__Answer__: The recommended way to use Raptor Templates with Express is to bypass the Express view engine and instead have Raptor Templates render directly to the response stream as shown in the following code:
 
 ```javascript
 var template = require('raptor-templates').load(require.resolve('./template.rhtml'));
 
 app.get('/profile', function(req, res) {
     template
-        .stream({
+        .render({
             name: 'Frank'
-        })
-        .pipe(res); 
+        }, res);
 });
 ```
 
 With this approach, you can benefit from streaming and there is no middleman (less complexity).
 
-Alternatively, you can use the independent [view-engine](https://github.com/patrick-steele-idem/view-engine) module to provide an abstraction that allows pluggable view engines and provides full support for streaming. This is shown in the following sample code:
+Alternatively, you can use the streaming API to produce an intermediate stream that can then be piped to the response stream as shown below:
 
 ```javascript
 var template = require('view-engine').load(require.resolve('./template.rhtml'));
diff --git a/runtime/raptor-templates-runtime.js b/runtime/raptor-templates-runtime.js
index 01b634e18..821d2f56f 100644
--- a/runtime/raptor-templates-runtime.js
+++ b/runtime/raptor-templates-runtime.js
@@ -74,7 +74,7 @@ Template.prototype = {
             }
             renderWithCallback(this, data, context, callback);
         } else {
-            if (context.attributes) {
+            if (context.isRenderContext) {
                 this._(data, context);
             } else {
                 // Assume the "context" is really a stream