On Thu, Sep 8, 2011 at 2:26 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm just wondering these kinds of things:<br>
<br>
- are pools necessary to get reasonable performance on highly loaded IdPs?<br></blockquote><div><br></div><div>I believe so, yes.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- do they handle failed connections reasonably without ever surfacing them<br>
as actual data connector failures?<br></blockquote><div><br></div><div>If they don't I hope someone files a bug report.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- are there ways to maintain connections and avoid the timeouts from the<br>
client end?<br></blockquote><div><br></div><div>You should be able to configure periodic validation to guarantee your connections are always alive.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- is pool validation even needed, or does it just retry on failures and<br>
handle things gracefully?<br></blockquote><div><br></div><div>Checkin/checkout validation is mainly just for the use cases I couldn't imagine. Connections will retry once by default on any communication error, so periodic validation provides the best benefit on top of that.</div>
<div> </div><div>--Daniel Fisher</div><div><br></div></div>