Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 10619 invoked from network); 30 Aug 2007 17:28:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Aug 2007 17:28:44 -0000 Received: (qmail 9617 invoked by uid 500); 30 Aug 2007 17:28:40 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 9597 invoked by uid 500); 30 Aug 2007 17:28:40 -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 9586 invoked by uid 99); 30 Aug 2007 17:28:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2007 10:28:40 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [134.129.111.44] (HELO mail2.sendit.NoDak.edu) (134.129.111.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2007 17:29:35 +0000 Received: from [134.129.71.65] (wings.cc.ndsu.NoDak.edu [134.129.71.65]) (authenticated bits=0) by mail2.sendit.NoDak.edu (8.13.8/8.13.1) with ESMTP id l7UHSDuC012861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 30 Aug 2007 12:28:13 -0500 Message-ID: <46D6FE2D.1080502@sendit.nodak.edu> Date: Thu, 30 Aug 2007 12:28:13 -0500 From: Richard Frovarp User-Agent: Thunderbird 1.5.0.12 (X11/20070718) MIME-Version: 1.0 To: users@directory.apache.org Subject: Supporting SOAP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org This may seem like an odd question, but how hard would it be to put a in a SOAP interface into DS to provide LDAP like functionality? We're working on a repository for identities that would coordinate amongst 12 institutions. We're not quite sure we want to commit to LDAP being the only way to get data in and out of the central repository and SOAP would provide a nice alternative. Any ideas? Thanks, Richard