Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 73094 invoked from network); 18 Mar 2008 09:14:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Mar 2008 09:14:29 -0000 Received: (qmail 79234 invoked by uid 500); 18 Mar 2008 09:14:26 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 79194 invoked by uid 500); 18 Mar 2008 09:14:26 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 79183 invoked by uid 99); 18 Mar 2008 09:14:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2008 02:14:26 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 18 Mar 2008 09:13:46 +0000 Received: (qmail 72984 invoked from network); 18 Mar 2008 09:14:05 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 18 Mar 2008 09:14:05 -0000 Message-ID: <47DF87DC.80607@apache.org> Date: Tue, 18 Mar 2008 10:14:04 +0100 From: Stefan Seelmann User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Ldif loader move ? References: <47DE3563.2060206@gmail.com> <2BDEADCB-E998-4A3F-89AD-3E8F21F058BD@yahoo.com> In-Reply-To: <2BDEADCB-E998-4A3F-89AD-3E8F21F058BD@yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi David, David Jencks schrieb: > > an even better solution? Also isn't there some code duplication on this > functionality between the server and studio? Yes, that is right. There are different LDIF parsers in studio and the server. The reason is that they must work differently: The studio LDIF parser is not just a LDIF-to-JNDI-translator but it is used for the LDIF editor feature. So it must be error tolerant to allow features like content assist and syntax highlighting. Kind Regards, Stefan Seelmann