Tomcat深入学习笔记(二):JNDI

xinxuaw231

　　JNDI Resources HOW-TO:
        JNDI现在一想起JNDI就知道利用它可以配置DataSource,别的还能开啥?不知道了.它本质上是干啥的?DataSource的什么特性与JDNI暗合后造成了现在我这样一提JNDI就只能想到DataSource?

        JNDI的产生背景?发展过程?它的利与弊?有没有别的什么替代物?好像跟JDBC有点关系.

        The JNDI architecture consists of an API (Application Programming Interface) and an SPI (Service Provider Interface). Java applications use this API to access a variety of naming and directory services. The SPI enables a variety of naming and directory services to be plugged in transparently, allowing the Java application using the API of the JNDI technology to access their services.

        看JNDI的API时看到javax.naming.ldap,(Lightweight Directory Access Protocol )也想起来现在项目中的用到了这个ldap.

        The JNDI SPI is designed to be used by arbitrary service providers including directory service providers. This enables a variety of directory and naming services to be plugged in transparently to the Java application (which uses only the JNDI API).
        
        A directory object provides an association between attributes and values. Thus, a directory service enables information to be organized in a hierarchical manner to provide a mapping between human understandable names and directory objects.

        
Naming -- The Foundation:(guide/jndi/spec/jndi/jndi.4.html)
    A fundamental facility in any computing system is the naming service - the means by which names are associated with objects, and by which objects are found given their names. In traditional systems, the naming service is seldom a separate service.

    Meaningful names can be composed using useful arrangements of naming services reflecting these relationships.

    The primary function of a naming system is to map names to objects.

    There can be multiple naming systems that can be represented by a composite namespace.

　　在JavaWorld上找了一个链接http://www.javaworld.com/javaworld/jw-01-2000/jw-01-howto.html,仔细看了看,很好,现在就很是需要这样的介绍性文章,结合实例,深入浅出,又很形象.