📄 c-overview1.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Tornado Architecture </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-overview.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-overview.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-overview.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-overview2.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="84386">1.1 Introduction</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84388"> </a>The central principles of the Tornado architecture are the following:</p></dl><dl class="margin"><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84389"> </a>Minimal intrusion on the target, by exploiting the development host as extensively as possible for interactive development tools.</li></ul></p><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84390"> </a>Centralized communications with the target, so that multiple development tools can share access to the target even when communications channels are limited.</li></ul></p><p class="listspace"><ul class="Bullet" type="disc"><li><a name="84391"> </a>Published protocols and application program interfaces (APIs) to make it simple to customize or extend Tornado.<div class="frame"><h4 class="EntityTitle"><a name="84396"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 1-1: Tornado Central Protocols: WTX and WDB</font></a></h4><dl class="margin"><div class="Anchor"><a name="84441"> </a><img class="figure" border="0" src="images/c-overview0.gif"></div></dl></div></li></ul></p></dl><dl class="margin"><dd><p class="Body"><a name="84442"> </a>The following two protocols are particularly important, because they mediate all contact between a Tornado tool and the target:</p></dl><dl class="margin"><dd><div class="Item"><a name="84444"> </a>WTX</div><dl class="margin"><dl class="margin"><dd><div class="Indent2"><a name="84445"> </a>The WTX (Wind River Tool eXchange) protocol specifies how the target server communicates with host-resident development tools. The protocol is extensible, to permit adding new services as required for new tool designs.</div><br></dl></dl><dd><div class="Item"><a name="84447"> </a>WDB</div><dl class="margin"><dl class="margin"><dd><div class="Indent2"><a name="84448"> </a>The WDB (Wind DeBug) protocol specifies how the target server (on the host) communicates with the target agent (on the target). The protocol includes a compact programming language called Gopher, which permits on-the-fly extension by supporting programmable investigation of the target system.</div><br></dl></dl></dl><dl class="margin"><dd><p class="Body"><a name="84452"> </a><a href="c-overview1.html#84396">Figure 1-1</a> illustrates the role of these two protocols in Tornado.</p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-overview.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-overview.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-overview.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-overview2.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -