On Jul 11, 12:31 pm, Jarkko Oranen <chous...@gmail.com> wrote > Forcing them into a single string at the end would wasteful in case > the user intends to write the output into a stream (which can be done > a fragment at a time.) Thus, leaving the choice to the user seems like > a good decision. > > Or maybe it's just a lazy seq, in which case using str on it would > force it to be strict. :)
Just to clarify . . . in order for this to be useful in practice, wouldn't the following be necessary: 1. Disable buffering in whatever server is being used to send the data (which in the case of http means losing the content-length header). 2. Lazy evaluation of all arguments to the template. Otherwise the client isn't going to get any content at all until the entire string has already been forced. . . or am I missing something? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
