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

grammar

Browse Source
This commit is contained in:
Trustin Lee 2008-12-30 02:12:56 +00:00
parent ac82b9fe0b
commit 54828269e4
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/java/org/jboss/netty/handler/codec/string/StringDecoder.java
View File

@ -50,7 +50,7 @@ import org.jboss.netty.handler.codec.oneone.OneToOneDecoder;
* // Encoder
* pipeline.addLast("stringEncoder", new {@link StringEncoder}("UTF-8"));
* </pre>
* and then you can use {@link String}s instead of {@link ChannelBuffer}s
* and then you can use a {@link String} instead of a {@link ChannelBuffer}
* as a message:
* <pre>
* void messageReceived(ChannelHandlerContext ctx, MessageEvent e) {

4
src/main/java/org/jboss/netty/handler/codec/string/StringEncoder.java
View File

@ -37,7 +37,7 @@ import org.jboss.netty.handler.codec.oneone.OneToOneEncoder;
/**
* Encodes the requested {@link String} into a {@link ChannelBuffer}.
* The typical setup for a text-based line protocol in a TCP/IP socket would be:
* A typical setup for a text-based line protocol in a TCP/IP socket would be:
* <pre>
* {@link ChannelPipeline} pipeline = ...;
*
@ -48,7 +48,7 @@ import org.jboss.netty.handler.codec.oneone.OneToOneEncoder;
* // Encoder
* pipeline.addLast("stringEncoder", new {@link StringEncoder}("UTF-8"));
* </pre>
* and then you can use {@link String}s instead of {@link ChannelBuffer}s
* and then you can use a {@link String} instead of a {@link ChannelBuffer}
* as a message:
* <pre>
* void messageReceived(ChannelHandlerContext ctx, MessageEvent e) {