directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christine Koppelt" <christine.kopp...@googlemail.com>
Subject Re: Apache Directory Frontpage Description Discussion
Date Mon, 28 May 2007 11:39:06 GMT
Hi Ole,

i agree with you, that the current version of this description isn't
optimal. I think we just copied it from a previous version. Feel free
to write a new text and add it to the site. Not sure if a diagram
makes sense at this place, this could make the site a bit unclear.

regards

Christine


2007/5/28, Ole Ersoy <ole.ersoy@gmail.com>:
> Hey Guys,
>
> I started looking at the front page description a little.
>
> Here's the current one:
>
> =============================================================
> Our primary vision is to build an enterprise directory server platform
> where other Internet services snap in to store their data within the
> directory so they may be managed using LDAP. Its architecture is
> designed so services other than LDAP such DNS, DHCP, SLP, Kerberos, and
> UDDI can be implemented and snapped in. These services will use a common
> networking layer (MINA) and each can be toggled on and off according to
> the needs of the environment.
> =============================================================
>
> Here are some thoughts:
>
> =============================================================
> Our primary vision is to build....
> =============================================================
> I think it's built...right...I'm thinking that when someone
> sees this they wonder...well how mature is this thing?
>
>
> =============================================================
> ....build an enterprise directory server platform where other Internet
> services snap in to store their data within the directory so they may be
> managed using LDAP
> =============================================================
> Hmmmm, so does LDAP do all the CRUD stuff, and other
> protocols/services piggy back on top of LDAP for their CRUD
> services or can they access the storage container
> directly without using LDAP?
>
> Also, seems like the project is rapidly outgrowing this...
> There's LS, etc. which I think should be reflected in the picture.
>
>
> =============================================================
> Its architecture is designed so services other than LDAP such DNS, DHCP,
> SLP, Kerberos, and UDDI can be implemented and snapped in.
> =============================================================
> This seems to partially repeat the previous statement.  Brevity
> and simplicity is key in getting the message across on the front
> page description, which hopefully results in more talent being
> brought down on the code.
>
> It also makes me wonder what implementations are there by default?
>
>
> =============================================================
> these services will use a common networking layer (MINA) and each can be
> toggled on and off according to the needs of the environment.
> =============================================================
> I think we have to put a bigger spotlight
> on it.  MINA is smoookkkkin right?  Footprint
> minimization by turning off stuff is coolll right?
>
> Although this still says "...will use" which makes
> it sound a little like the project is just starting...
>
> Here's a suggestion for a description revision (This needs
> a lot of work - I'm trying to zoom in on what Apache Directory
> is right now as accurately and simply possible - In other
> words this part and here is the point of this part
> here's the point of the part as simply and briefly as possible):
>
> =============================================================
> The Apache Directory consists of:
> - A container for protocols like LDAP, UDDI, DNS, DHCP, etc.
> - A set of default protocol implementations
> - A container supporting different data storage implementations.
> - A set of data storage implementations.
> - An embeddable server for configuring container services and
>    and service implementations, as well as turning them
>    on or off.  LDAP is the only protocol implementation
>    on by default, minimizing the servers footprint.
> - Server Embedding API
> - A high performance networking layer (MINA)
> - Developer Tooling (Ldap Studio)
> - Security stuff....(Triplesec)
> - Multi Master Replication stuff
> - Other stuff....In case I missed something...
> =============================================================
>
> Note that this does away with the term "Internet" in the description.
>
> Also "...snapped in" is gone.  Sorry - had to be put down.  It's still
> on the main page though, so you can say hello whenever.
>
> I'm also planning to get a summary diagram going for this stuff,
> that I was hoping would get put below the description, if we think
> it's appropriate.  Sort of depends on the diagram right :-)
>
> Thoughts?
>
> Cheers,
> - Ole
>

Mime
View raw message