• Program options:
    • Slide:
      • Inadequate: the final version of its open source components was in 2004, in recent years are no longer updated
      • Slide item a few very poor place to do:

        1, the positioning of the plan from the project point of view it is to achieve the WebDav standard, WebDav for enterprise content management applications is a very attractive location from the project point of view, there are two aspects of the division of work, that is, WebDav service WebDav-based applications, Slide are the two working together, and the consequences of not doing the work are two.

        2, the contents of the code from the version presented, the absence of a lot of content, such as version control, full-text search and so on, read the Project if, and then read the contents of the achievement, too much contrast, we saw it in many parts of the code one will know.

        3, application design, and sometimes I have the feeling that the functions of the project designers did not know what they are doing, enterprise content management what to do in the end? The definition of document object, document handling process is messy, if the application integration and it should be amended by the workload is tremendous.

        Apache-based systems and services for engines of some of the projects in this area do a good service if we do, and so the application of the project applications are often very poor, giving us the feeling that several little experience doing. Services and applications at the same time of very tight coupling, it is not a detailed analysis of the code, it is difficult to split up the project again if a framework based on Apache, such as Turbine, basically announced that you will not use this item a, Jetspeed also has this diseases.
    • Milton:

    • Jackrabbit: