From users-return-5197-apmail-directory-users-archive=directory.apache.org@directory.apache.org Mon Mar 11 17:16:48 2013 Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 51B10D407 for ; Mon, 11 Mar 2013 17:16:48 +0000 (UTC) Received: (qmail 95812 invoked by uid 500); 11 Mar 2013 17:16:48 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 95698 invoked by uid 500); 11 Mar 2013 17:16:47 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 95682 invoked by uid 99); 11 Mar 2013 17:16:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 17:16:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.223.181 as permitted sender) Received: from [209.85.223.181] (HELO mail-ie0-f181.google.com) (209.85.223.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 17:16:43 +0000 Received: by mail-ie0-f181.google.com with SMTP id 17so5130598iea.12 for ; Mon, 11 Mar 2013 10:16:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=fTtFLP2N3nE1dsSHmiNjOCIqakESsXe4/0KgQhZbarU=; b=GSI0XyP/7gc30RsoTW33z6YM+jhn1JKjR0Y1H2mS+rQNBftBsvrOFFJSEMoS/LkmMW PQlSrFHDP3VkeD2uSrwQ0DzMihOHulhdDSUAKdTslRNQ/jN6pZgg9xevBIEevqUL+KFL SpV/7PZMxJltEGDxE6fG46KvcVcZWKixLW1rdYWFp69T7A/BJWQlGhi6K02+m9OtPpzH bI0lZqUbXovfJJUatEcz10UV+wJyasW+MZadkzyZNimUC1tCa4jvBS7zcdt/s56F8NZ5 eYAe+IsKMchvSVlUK8ejTnOxOv89IskJf5/GVSsU7rH8mku52zBagLDl5dwqyggrWEA3 r9jw== MIME-Version: 1.0 X-Received: by 10.50.140.101 with SMTP id rf5mr7998979igb.41.1363022182655; Mon, 11 Mar 2013 10:16:22 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.231.72.67 with HTTP; Mon, 11 Mar 2013 10:16:22 -0700 (PDT) In-Reply-To: <002c01ce1e7b$061fc880$125f5980$@tombruser.com> References: <002c01ce1e7b$061fc880$125f5980$@tombruser.com> Date: Mon, 11 Mar 2013 22:46:22 +0530 X-Google-Sender-Auth: yNrQBWr_sgHY7TM4-S9V8rPbPfg Message-ID: Subject: Re: Continuation of evaluation of ApacheDS as part of a preemptive cache From: Kiran Ayyagari To: users@directory.apache.org Content-Type: multipart/alternative; boundary=e89a8f923bd604b3cd04d7a9558c X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f923bd604b3cd04d7a9558c Content-Type: text/plain; charset=ISO-8859-1 On Mon, Mar 11, 2013 at 10:38 PM, Tom Bruser wrote: > I've been making some progress in standing up a memory partition for > ApacheDS and still have some ways to go to make a custom partition to store > the data as I see better fit for my purposes. > > My preemptive cache will be available to *most* of our clients via a simple > restful service call. The purpose of looking at ApacheDS is to deal with > one client that is set up to only talk to LDAP. This client will > essentially connect in to LDAP and perform a simple search. Think in terms > of an out of the box CMS that needs to import its users and groups > information. > > Just to make sure I'm not trying to over-architect the solution, is there a > better way to provide a facility to let an LDAP client bind (log in), > interpret or parse the LDAP query (filter) into something that can query > against simple collections of POJOs, and return an LDAP-friendly response? > This is based on my current direction to stand up ApacheDS and customize a > memory partition so that it can map to my POJOs. It just seems so far > that, > albeit possibly due to ignorance, am trying too hard to structure my > in-memory data to cater to how ApacheDS would like to see it represented as > opposed to just trying to figure out what the client is asking for and find > it within the structure that I'm already planning to use for the other 90% > of clients. I've seen some mention of FilterParser, but did not yet find > much information on how to use it... of course, I'd still need a means to > accept the filter from the client to begin with even once I learn how to > use > it. > > the best way is to override the search( SearchOperationContext searchContext ) method in your custom partition, The parsed filter is available as a java object (ExprNode) saving your time from parsing from there you are on your own with your logic :) Please post here if in case you encounter any hurdles while trying to achieving what you need. -- Kiran Ayyagari http://keydap.com --e89a8f923bd604b3cd04d7a9558c--