HttpClient in Scripted Attribute Example

[Nate Klingenstein]

> Interesting approach…

It's the laziest conceivable way to provision users dynamically.  I
plan to use it heavily.

> I’m curious what would happen if that URL were unavailable/erroring or, perhaps worse, taking a really long time to respond.

Immediate errors without a try block return immediate 500's.  With a
try block, I can just log the error along with the URL at WARN and
send the user along(if this is a desired outcome).  I don't plan on
misappropriating this for user-facing errors, though.

The library gives you significant control over timeouts, and that is
going to be the extent of my fine tuning.

There's nothing sensitive about this provisioning and the network is
secured anyway, so I can do this safely.  We have other, less elegant
situations that may require actual thinking.  In those instances, I
hope to abuse the future HTTP Data Connector.