per-entity - RE: [Per-Entity] MDQ server software
Subject: Per-Entity Metadata Working Group
List archive
- From: "Cantor, Scott" <>
- To: Tom Scavo <>
- Cc: "" <>
- Subject: RE: [Per-Entity] MDQ server software
- Date: Mon, 18 Jul 2016 13:50:51 +0000
- Accept-language: en-US
- Authentication-results: spf=pass (sender IP is 164.107.81.220) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=bestguesspass action=none header.from=osu.edu;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
> If, for instance, apache can be configured to support the MDQ
> protocol, I'd be pleasantly surprised. In any case, maybe Ian can
> address this question on Wednesday's call?
I think I'm safe in saying that if it can't, the MDQ spec needs to be
tweaked. I'm very sure that was an intended design constraint on the
protocol. HTTP and not much else, very lightly profiled in ways that either
don't matter all that much or should be easy to configure any full-featured
web server to handle.
I'm also speaking specifically of the per-entity use case, minus custom
queries, since that was I think explicitly left out of scope of this group.
-- Scott
- [Per-Entity] MDQ server software, Tom Scavo, 07/18/2016
- RE: [Per-Entity] MDQ server software, Cantor, Scott, 07/18/2016
- Re: [Per-Entity] MDQ server software, Tom Scavo, 07/18/2016
- RE: [Per-Entity] MDQ server software, Cantor, Scott, 07/18/2016
- Re: [Per-Entity] MDQ server software, Tom Scavo, 07/18/2016
- RE: [Per-Entity] MDQ server software, Cantor, Scott, 07/18/2016
Archive powered by MHonArc 2.6.19.