清单10显示了对等的JiBX取消包装代码。
和ADB取消包装代码类似，理解和使用服务调用的取消包装形式比使用直接代码简单得多。
As with the ADB unwrapped code, it's much easier to understand and work with the unwrapped form of the service calls than with the direct code.
与其将非托管代码权限授予所有使用这些包装的应用程序，不如只将这些权限授予包装代码。
Instead of giving all applications that use these wrappers unmanaged code rights, it is better to give these rights only to the wrapper code.
在这种情况下，受信任的代码可以充当中介，它类似于保护包装代码中所述的托管包装或库代码。
In such cases, your trusted code can be the go-between, similar to the managed wrapper or library code described in Securing wrapper code.
包装代码可能会暴露一组特殊的安全弱点，尤其是在包装比使用它的代码拥有更高程度的信任的情况下。
Wrapper code, especially where the wrapper has higher trust than code that USES it, can open a unique set of security weaknesses.
但是发明了JSON 之后，服务器端代码可以包装和发送 JSON 编码的应用程序数据来响应浏览器请求。
With the advent of JSON, however, the server-side code can package and ship JSON-encoded application data in response to the browser requests.
清单5显示了生成对包装方法的调用并保存结果(如果有的话)的代码。
Listing 5 shows the code to generate the call to the wrapped method and save the result (if any).
依我看，它提供了一个连接池把传入代码包装在纤程当中，等到连接可用的时候再恢复纤程。
As I see, it allows to pass code wrapped in Fibers to a pool of connections, which then resumes the Fibers as connections become available.
只要有可能，常用的代码应该被包装进框架或者库里面，不需要整天看到它们。
When possible, commonly used code should be wrapped up in frameworks and libraries where you don't have to look at it.
这三个方法实质上都是先前开发的数据访问代码的包装器。
Each of these is essentially a wrapper around the data-access code we developed earlier.
开发这些面向数据应用程序的数据访问开发人员可以证实，他们常常需要将DML(数据操纵语言)包装到很多代码中。
Data access developers who develop these data-oriented applications can attest to the fact that it typically requires wrapping DML (data manipulation language) statements in a fair amount of code.
因此，在使用预包装的代码时，我们如何能够创建一个瘦的、聚焦于质量的软件开发环境？
So how can we create a lean, quality-focused software development environment while working with pre-packaged code?
通过上面可以看出，数据对象包装组成了应用程序代码的主要部分。
As you can see from the above, data object wrappers constitute a major part of an application's code.
清单2和清单3是一个简单的PHP应用程序，其中包含一个类、方法和一些包装器代码。
Listing 2 and Listing 3 show a simple PHP application with a class, methods, and some wrapper code.
但是，通过包装与MDA核心模型一致的代码层，遗留应用程序也可以引入到MDA中。
Legacy applications may be brought into the MDA, however, by wrapping them with a layer of code that is consistent with an MDA core model.
您需要通过现有代码来跟踪用户输入，而不能用验证函数包装您看到的每个变量。
You need to trace user input through existing code to see if the application behaves securely, instead of wrapping every variable you see in a validation function.
包装外观中所含的遗留代码的典型示例是一组相关模块，这些模块负责与远程语音设备管理平台进行交互。
A typical example of legacy code contained by a wrapper-facade was a group of related modules responsible for interacting with a remote telephony-device management platform.
代码的包装将解析XML输入数据，并将值传递到包装组件中相应的位置。
The wrapper of the code parses the XML input data and moves the values to the appropriate addresses in the wrapped component.
该包装类将参数格式化为类似上面代码的XML字符串。
The wrapper class would take care of formatting the arguments into an XML string resembling the code above.
当向服务器发送XML的时候，更多的代码用于获取数据和包装成xml，而不是真正的传输数据。
When it comes to sending XML to the server, you'll spend more of your code taking your data and wrapping it XML than you will actually transmitting the data.
返回代码被传递回到包装器，后者再将其传递回到您自己的代码。
The return code is handed back to the wrapper, which hands it back to your code.
类包装背后的理念是：目标类可以包装在一层插装代码中，后者具有与被包装的类相同的外部行为。
The idea behind class wrapping is that a target class can be wrapped in a layer of instrumenting code that retains the same external behavior as the class that's wrapped.
也就是说，在64位环境中，用32位包装器和桥接代码运行的SELECT比在相同数据源上用隔离的64位包装器运行的同样的查询仅慢1%。
That is, SELECTs run with a 32-bit wrapper and the bridging code in a 64-bit environment were only 1% slower than the same queries run with a fenced 64-bit wrapper for the same source.
注意注释代码和包装器之间的相似之处；这让您感觉到将要写什么样的代码。
Note the similarity between the commented code and the wrapper; that's to give you a sense of what code you're trying to write.
在上面的代码中，请注意，不能只是将String包装在直接ByteBuffer中。
In the code above, notice that you can't just wrap the String into a direct ByteBuffer.
该代码允许其他小部件将数据传递到包装器iWidget。
This code allows other widgets to pass data to the wrapper iWidget.
SJ：JBI是引擎到引擎(engine - to - engine)的，SCA包装了引擎中的代码。
SJ: JBI is engine-to-engine, SCA wraps up the code in the engines.
包装器代码将是Web服务，并且它将委派真正实现的所有调用。
The wrapper code would be the Web service, and it would delegate all invocations to the real implementation.
可以简单地将XHTML 代码包装在Atomenvelope 中，从而给应用程序添加联合支持，但是从纯粹的面向数据角度来看，Atom没有给我提供任何好处。
I could simply wrap my XHTML example in an Atom envelope to bring syndication support to my application, but from a purely data-oriented view, Atom is not bringing me any advantages.
既然我们有了界面定义，那么就可以生成Python包装器的代码块。
Now that we have the interface definition, we can generate the bulk of the Python wrapper.
应用推荐