andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update on the previous documentation effort

Browse Source
This commit is contained in:
Trustin Lee 2009-04-06 12:02:38 +00:00
parent 1e00b56a70
commit 67edb9d69d
1 changed files with 16 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
src/docbook/module/architecture.xml
View File

@ -182,25 +182,25 @@ dynamicBuffer.writeByte('7');</programlisting>
to be in trouble when your business grows up exponentially and your server to be in trouble when your business grows up exponentially and your server
starts to serve tens of thousand clients simultaneously. You could starts to serve tens of thousand clients simultaneously. You could
start with NIO, but it might take much longer time to implement due to start with NIO, but it might take much longer time to implement due to
the complexity of the NIO Selector API, hindering your business. the complexity of the NIO Selector API, hindering rapid development.
</para> </para>
<para> <para>
Netty has a central interface called &Channel;. &Channel; abstracts away Netty has a universal asynchronous I/O interface called &Channel;
all operations required to point-to-point communication. That is, once &Channel; abstracts away all operations required to point-to-point
you wrote your application on one Netty transport, your application can communication. That is, once you wrote your application on one Netty
run on other Netty transports in most cases. Netty provides the following transport, your application can run on other Netty transports. Netty
transports via this universal I/O API: provides a number of essential transports via one universal API:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
NIO-based TCP/IP transport NIO-based TCP/IP transport
(see <literal>org.jboss.netty.channel.socket.nio</literal>), (See <literal>org.jboss.netty.channel.socket.nio</literal>),
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
OIO-based TCP/IP transport OIO-based TCP/IP transport
(see <literal>org.jboss.netty.channel.socket.oio</literal>), (See <literal>org.jboss.netty.channel.socket.oio</literal>),
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@ -208,21 +208,20 @@ dynamicBuffer.writeByte('7');</programlisting>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Local transport for communication between two Netty applications in Local transport (See <literal>org.jboss.netty.channel.local</literal>).
the same VM (see <literal>org.jboss.netty.channel.local</literal>).
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
For instance, you could start to write your application with OIO-based Switching from one transport from the other usually takes just a couple
UDP/IP transport first, add TCP/IP support using the OIO-based TCP/IP lines of changes such as choosing a different &ChannelFactory;
transport, and then replace the OIO-based TCP/IP transport with the implementation.
NIO-based TCP/IP transport to handle more concurrent connections, all by
replacing just a couple lines of constructor calls in the source code.
</para> </para>
<para> <para>
Also, you will even be able to take advantage of a new transport which is Also, you will even be able to take advantage of a new transport which is
going to be added to Netty, again by replacing just a couple lines of not written yet, serial port communication transport for instance, again
constructor calls. by replacing just a couple lines of constructor calls. Moreover, you can
write your own transport by extending the core API because it is highly
extensible.
</para> </para>
</section> </section>