Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com
 designates 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
        b=mf3IeGDpeTJ8VT0s7CpnxoXCBja9wLJJ0GWqFnaP3ZkTeBLupWCt0RACKqkUTS2P5/hVQ3zV/RslW8cXm3IVH0SBZSnZ2GqHBHzgGb8o3x0oGNm9JBUuuHpUoNuZNhy84zEfDDrjYBbDfYOJcO81+u4u/roNIZmtGkPHLxgsCcM=
Message-ID: <a32f6b020708290722i60649c69ye203958e786de8a1@mail.gmail.com>
Date: Wed, 29 Aug 2007 10:22:25 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: [LDAP][Client] Slick idea for a CLI based client
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2019_19570231.1188397345559"

------=_Part_2019_19570231.1188397345559
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

A while back I posted some Confluence pages about writing a command line yet
interactive
LDAP client called LDAP shell.  I never really got any comments about it.  I
just thought
it might be worth while putting out the idea again on this email channel.

The concept is simple and one that everyone on the command line is pretty
much used to.
A shell.  Users log into an LDAP server and have a command prompt where they
can:

 o CD into any ldap context using relative or absolute distinguished names
 o LS within a server entry to list it's children if any (use -R to change
scope :))
 o CAT to print the contents of an entry to the console
 o LESS to pan through contents
 o VI, ED to edit the contents and save
 o PUSHD to push a DN onto the stack
 o POPD to pop a DN off of the stack and CD into it
 o MV to modifyDn on an entry
 o CP to copy an entry

Yep all the shell built-ins you're used to in bourne or bourne again shells
should be there.  The
only difference in the commands are that they apply to a different naming
system than the UNIX
file system path syntax.

The idea here is to enable LDAP scripting for those who already know how to
script in shells.
Furthermore these deterministic scripts can be transformed into code that
can be pushed into
the server as stored procedures.

Also Directory Studio can use this as an LDAP console.  You don't need to
just be in a shell
to utilize this neat little client.  Studio's browser can select nodes in
the tree to represent
the path of working directory ($PWD).  As the user navigates through the
LDAP shell Studio's
browser can give them cues on their position and where they can go. Drag and
drop can be
used to move nodes in the browser into the shell which will list the DN of
the node dropped in.
Selected a node in the browser can automatically CD users into that entry.

Is this a crazy idea? Thoughts?

Alex

------=_Part_2019_19570231.1188397345559
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

A while back I posted some Confluence pages about writing a command line yet interactive <br>LDAP client called LDAP shell.&nbsp; I never really got any comments about it.&nbsp; I just thought<br>it might be worth while putting out the idea again on this email channel.
<br><br>The concept is simple and one that everyone on the command line is pretty much used to.<br>A shell.&nbsp; Users log into an LDAP server and have a command prompt where they can:<br><br>&nbsp;o CD into any ldap context using relative or absolute distinguished names
<br>&nbsp;o LS within a server entry to list it&#39;s children if any (use -R to change scope :))<br>&nbsp;o CAT to print the contents of an entry to the console<br>&nbsp;o LESS to pan through contents <br>&nbsp;o VI, ED to edit the contents and save
<br>&nbsp;o PUSHD to push a DN onto the stack<br>&nbsp;o POPD to pop a DN off of the stack and CD into it<br>&nbsp;o MV to modifyDn on an entry<br>&nbsp;o CP to copy an entry<br><br>Yep all the shell built-ins you&#39;re used to in bourne or bourne again shells should be there.&nbsp; The 
<br>only difference in the commands are that they apply to a different naming system than the UNIX<br>file system path syntax.&nbsp; <br><br>The idea here is to enable LDAP scripting for those who already know how to script in shells.&nbsp; 
<br>Furthermore these deterministic scripts can be transformed into code that can be pushed into<br>the server as stored procedures.&nbsp; <br><br>Also Directory Studio can use this as an LDAP console.&nbsp; You don&#39;t need to just be in a shell
<br>to utilize this neat little client.&nbsp; Studio&#39;s browser can select nodes in the tree to represent <br>the path of working directory ($PWD).&nbsp; As the user navigates through the LDAP shell Studio&#39;s<br>browser can give them cues on their position and where they can go. Drag and drop can be 
<br>used to move nodes in the browser into the shell which will list the DN of the node dropped in.<br>Selected a node in the browser can automatically CD users into that entry.<br><br>Is this a crazy idea? Thoughts?<br><br>
Alex<br>

------=_Part_2019_19570231.1188397345559--