KBMMW简介

This description only touches a tiny subset of the facilities provided by the kbmMW™ n-tier framework. For more complete info, please check the kbmMW™ feature matrix and visit the kbmMW™ university. 这个介绍只涉及到 KBMMW多层框架提供的很小部分的功能。想要获得更多信息，请查看KBMMW特性，并浏览KBMMW大学。 You may have heard about 2-tier and n-tier applications. What are they exactly? 你可能有听说2层架构的应用，他们到底什么？ 2-tier - also called client/server - applications are applications which consist of two separate applications, one server application (typically a database server like Oracle, MSSQL or any other standalone database) and a client application. 2层 （也被称作客户机/服务器模式）应用程序是由两个独立的应用程序组成，一个是服务器端应用（典型的是一个数据库服务器，如Oracle、Mssql或者其他独立的数据库），另一个是客户端应用程序。 n-tier applications consist of 3 or more active applications which data must pass, from the backend server to the front end client. Usually 3-tier models are used, where one tier is the backend database engine, one is the front end client and one is just in between them, also named the application server or business logic node. 多层应用包含3个或者更多的活动的应用，数据必须有后端服务器到客户端，通常，通常使用3层模型。其中，一层是后端数据库引擎，一个是前端客户，另一个是位于他们之间，也被称作应用服务或者业务逻辑。 What is the purpose of having more than 2 tier? 具有多于2层架构的目的是什么？ Well.. if you want to have many different client frontends, like f.ex. one written in Delphi/C++Builder/.Net as a normal fat client, one as a web server, one as a WAP server, one as a linkup server to a mainframe etc. it would be unwise to copy all the business logic (all the rules of your application) to each client application/server. It would be a nightmare to support. Instead its better to create a middle layer containing the business logic, and then let the clients talk with this middle layer. Thus the clients can relatively easily be changed for other types of clients, without need for remembering how was the business logic put together. 如果你想要很多不同的前端客户端，比如f.exe 是一个用delphi或者C++或者.net写成的正常的富客户端。一个用来做web服务器，一个用于wap服务器，一个为连接到大型机的服务器等等。复制所有的业务逻辑（所有你应用程序的规则）到每一个客户端应用或者服务器是不聪明的做法。它将成为技术支持的噩梦。相反之下，创建一个包含业务逻辑的中间件并让客户端与这个中间件通信是更好的。因此，这个客户端便能相对容易的改变成其他类型的客户端而无需记忆这些业务逻辑是怎么放在一起的。 Using n-tier models also gives other positive side effects: 使用多层模式也能提供以下正面的效果： -装载平衡。 相比两层解决方案具有服务更多个客户端的能力，简单地说，因为中间节点（应用服务器）可以被复制到多以一个的机器中，因此更多CPU分散了装载压力。 -容错 。如果更多应用服务器都在运行，在一个服务器没有回复的情况下，这些客户单可以简单尝试请求另一个应用服务器。 - Load balancing. They are capable of serving many more clients than a 2-tier solution, simply because the middle node (the application server) can be copied to more than one machine, and thus divide the load between more CPU's. - Fault tolerance. If more application servers are running, the clients can simply try the request on another appserver if the first one didnt reply. kbmMW™ is about all that and much more. It will support different database backends directly without you having to write any code. Thus if you need to perform a SQL query you will do it much the same way you are used to in a normal 2-tier setup. The specialized client and server service classes will handle everything for you. kbmMwis关于所有的这些甚至更多，他将直接支持不同的数据库端而无需你写任何代码。因此当你你需要执行一个SQL查询，你只需做很一些像和正常使用2层设置的相同的工作。指定客户端和服务器类将为你处理所有的事情。 Further kbmMW™ contains advanced connection pooling on both client to server and server to database, caching of result sets on both client to server and server to database and much more. 更进一步，kbmMW在客户端到服务器和服务器到数据库均包含先进的连接池，用于缓存所有服务器到客户端和客户端到服务器甚至更多的数据集。 The database handling with its advanced caching and connectionpooling can actually be used in 2-tier (Client/Server) setups aswell without using the remaining part of kbmMW™ giving you freedom in creating your application or web application the way you want to. 数据库使用他的高级缓存和连接池可以被用于2层（客户端/服务器）配置，同样地没有使用kbmMW的部分让你在创建你的应用或者web应用你想要的自由度。 kbmMW™ contains countless features to integrate with the world, and can mimic as a SOAP server, a WEB server, a AJAX server, a AMF3 server and much more. It also contains one of the most advanced messaging framework for Delphi/C++Builder/Kylix, supporting multiple topologies incl. Peer 2 Peer, Hub/Spoke and Broadcast using Publish/Subscribe based messaging via multiple types of fully developer accessible and configurable  message queues. kbmMW包含了数不尽的特性来集成整个世界，它可以模仿成一个SOAP服务器，一个WEB服务器，一个AJAX服务器、一个AMF3服务器以及更多。它也包含了所有Delphi/C++中高级消息框架的一个。支持多种拓扑结构，包括点到点，中心式和使用基于消息通过多种不同类型开发可访问和可配置的消息队列。 There are no runtime fees or royalties except for the developer licenses. The source is fully included in the package. The kbmMW University provides all the currently published documents regarding kbmMW. This includes whitepapers and help files. The documents are organized in the following categories: kbmMW大学提供所有当前发布的关于kbmMW的文本。包括白皮书和帮助文件。这些文档有： Essential   必须的 Recommended  推荐的 Specialized   专业版 Highly technical  高级技术 The order of the documents shown on this page indicates the suggested order in which they should be read. 这些在本页面展示的文档的次序已经表明了建议阅读他们的次序。 In the Description column, a kbmMW™ versionnumber is specified. It indicates what version of kbmMW™ must be used as a minimum for the document to match. A plus after the version number indicates that the document match later versions of kbmMW™ too. 在这个描述栏目，指定了kbmmw的版本号。他表明什么kbmMw的版本必须被使用做一个最小的 In the Edition column, the type of kbmMW™ license required, is listed: E=Enterprise Edition PP=ProPlus Edition P=Pro Edition S=Standard Edition F=Freeware Edition C=CodeGear Edition