per-entity - RE: [Per-Entity] Serving mdq queries with Apache

Subject: Per-Entity Metadata Working Group

List archive

RE: [Per-Entity] Serving mdq queries with Apache

From: "Cantor, Scott" <>
To: Tom Scavo <>, Tom Mitchell <>
Cc: "" <>
Subject: RE: [Per-Entity] Serving mdq queries with Apache
Date: Thu, 28 Jul 2016 19:22:22 +0000
Accept-language: en-US
Authentication-results: spf=pass (sender IP is 164.107.81.208) smtp.mailfrom=osu.edu; bbn.com; dkim=none (message not signed) header.d=none;bbn.com; dmarc=bestguesspass action=none header.from=osu.edu;
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

> The MDQ server needs to support both.

Right. Generally what you would do is pre-hash and store them that way.
Turning a URL encoded entityID into the hash is a trivial shell-scripting
exercise or could also be table-driven of course, or you could store under
both locations to make it remain static.

-- Scott

[Per-Entity] Serving mdq queries with Apache, Tom Mitchell, 07/28/2016
- Re: [Per-Entity] Serving mdq queries with Apache, David Walker, 07/28/2016
  - Re: [Per-Entity] Serving mdq queries with Apache, Tom Mitchell, 07/29/2016
    - Re: [Per-Entity] Serving mdq queries with Apache, Walter Forbes Hoehn (wassa), 07/29/2016
      - Re: [Per-Entity] Serving mdq queries with Apache, David Walker, 07/29/2016
      - Re: [Per-Entity] Serving mdq queries with Apache, Walter Forbes Hoehn (wassa), 07/30/2016
- Re: [Per-Entity] Serving mdq queries with Apache, Tom Scavo, 07/28/2016
  - RE: [Per-Entity] Serving mdq queries with Apache, Cantor, Scott, 07/28/2016
  - Re: [Per-Entity] Serving mdq queries with Apache, Tom Scavo, 07/28/2016
    - Re: [Per-Entity] Serving mdq queries with Apache, Tom Mitchell, 07/28/2016
  - Re: [Per-Entity] Serving mdq queries with Apache, Walter Forbes Hoehn (wassa), 07/28/2016
  - Re: [Per-Entity] Serving mdq queries with Apache, Tom Mitchell, 07/28/2016

List archive

RE: [Per-Entity] Serving mdq queries with Apache