<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Oct 4, 2011, at 2:26 PM, Norbert Hartl wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>And still what you are saying is correct that whatever I tell you the extra request goes on top. I just want to add that the effect is not as big as you might think.</div><div><br></div><div>Norbert</div></span></blockquote></div><div><br></div><div><br></div><div>perhaps, but we should rely on the measured observations on how it performs with redirects vs. without them.</div><div><br></div><div>Probably not for everybody but there is something else: </div><div><br></div><div>For all people using<i> one transaction per request </i>kind of architectures...</div><div><br></div><div>Having the redirect means that your app needs 2 transactions per action with all the overhead and complications that it could mean*.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><a href="http://about.me/sebastianconcept">sebastian</a></div><div><br></div><div>o/</div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div><div>*for example the data your app readed fresh in the first transaction has no use on the second complicating the app (if consistency is mandatory it probably requires a re-read). Depending on how the app deals with that problem, that could be a hidden cost (paid in latency in the magnitude of I/O and in development costs)</div><div><br></div>
<br></body></html>