Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] A little MDQ mvp in AWS

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] A little MDQ mvp in AWS


Chronological Thread 
  • From: Nicholas Roy <>
  • To: <>
  • Subject: Re: [Per-Entity] A little MDQ mvp in AWS
  • Date: Thu, 13 Oct 2016 10:54:41 -0600
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:Zp8xDh0EGiGd/h2asmDT+DRfVm0co7zxezQtwd8ZsesQL/ad9pjvdHbS+e9qxAeQG96Eu7QZ0KGP7ujJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6i760TlHTg3yL094IPj0Bp/6jsK80OW3/JuVZB9H0mmTe7R3eTO3pgXWssANybFlO+5lzAHOs1NJffhb32VlOQjVkhrhsJTjtKV/+jhd7qpyv/VLVr/3Kvw1
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99


On 10/13/16 10:47 AM, Cantor, Scott wrote:
Ah, so the concern is that a node goes away in the middle of serving
a metadata request to the client. And, the client would not recover or
retry the request?
Defining "in the middle" as between the time the client is given a particular address
and the request is made or completes, yes. Browsers now fetch all A records and auto-failover to
all of them, so if you have aggressive timeouts, you get what appears to be a reliable system
when you're serving largely static content. Non-browsers don't, and in some cases probably can't,
even if they wanted to. The model just doesn't work for "services" very well.

It may be that REST clients are starting to evolve to compensate for this,
but my initial research doesn't suggest to me that either Java nor libcurl
are doing this, so that covers Shibboleth.

I had to invent some really disgusting .NET code at one point to do this for a client I was developing. I doubt it would be possible in Java, but in .NET there is enough DNS functionality exposed in the base class libraries that it was possible.

Nick


-- Scott





Archive powered by MHonArc 2.6.19.

Top of Page