<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 28, 2016, at 12:43 PM, Helge Heß via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="">swift-server-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I think that no one debates that they have issues. I think the key point was that most/all of those issues need to be solved in Foundation too and that it doesn’t make sense to have two variants of them.</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote></div><br class=""><div class="">Sorry I didn't see those threads earlier, but I'm in complete agreement. I've been holding off proposing new API internally pending the outcome of these discussions.</div><div class=""><br class=""></div><div class="">For my (selfish) purposes, I'd prefer a new set of objects that are almost-but-not-quite the existing objects. (I prefer policy (caching, timeouts) be tied to a session configuration rather than to the request object itself.). </div><div class=""><br class=""></div><div class="">--sma</div><div class=""><br class=""></div></body></html>