nothing :)<div><br><div>Rails will also be able to flush the head of the page to the client and stream the rest of the response to allow the client to begin asset downloading earlier while the rest of the page is constructed. Something we could look into, but it adds complexity and it remains to be seen if that actually translates to noticeably better performance.</div>

<div><br></div><div>Greg Weber<br>
<br><div class="gmail_quote">On Tue, Jun 7, 2011 at 8:21 AM, Max Cantor <span dir="ltr">&lt;<a href="mailto:mxcantor@gmail.com" target="_blank">mxcantor@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


all my rails friends are shitting themselves about some new &quot;asset pipeline&quot; which takes your individual css and js files and minifies and combines them into a single file to send to clients.  as far as I can tell, this brand-new-killer-omfg-feature is what yesod has been doing from the beginning.  what am I missing?<br>



<br>
max<br>
<br>
<br>
_______________________________________________<br>
web-devel mailing list<br>
<a href="mailto:web-devel@haskell.org" target="_blank">web-devel@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
</blockquote></div><br></div>
</div>