<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 5, 2015 at 9:04 AM, Chris Cunnington <span dir="ltr"><<a href="mailto:brasspen@gmail.com" target="_blank">brasspen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><br>
But I suppose this is really about buffer size and flushing
frequency. I imagine Seaside could chunk its responses, but instead
saves every response into one large buffer and then flushes once. <br>
With Altitude I can put 'self halt' in the middle of a page and
watch half a a page render. The buffer size is set to 1K and flushes
when the buffer is full, which doesn't take long. <br></div></blockquote><div><br></div><div>Right. Seaside feels slower, even when the rendering time is the same. However, Seaside handles application errors more gracefully than Altitude. If there's an error halfway down the page, Seaside catches it and sends a nice error page page to the browser, with a walkback and a debug link. Altitude can't do that, since the headers and half the page have already been sent. Different tradeoffs.</div><div><br></div><div><br></div></div></div></div>