Deprecated API


Contents
Deprecated Classes
org.jboss.netty.handler.codec.serialization.CompatibleObjectDecoder
          This decoder has a known critical bug which fails to decode and raises a random exception in some circumstances. Avoid to use it whenever you can. The only workaround is to replace CompatibleObjectEncoder, CompatibleObjectDecoder, ObjectInputStream, and ObjectOutputStream with ObjectEncoder, ObjectDecoder, ObjectEncoderOutputStream, and ObjectDecoderInputStream respectively. This workaround requires both a client and a server to be modified. 
 

Deprecated Methods
org.jboss.netty.channel.Channels.bind(ChannelHandlerContext, Channel, ChannelFuture, SocketAddress)
          Use Channels.bind(ChannelHandlerContext, ChannelFuture, SocketAddress) instead. Sends a "bind" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.close(ChannelHandlerContext, Channel, ChannelFuture)
          Use Channels.close(ChannelHandlerContext, ChannelFuture) instead. Sends a "close" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.connect(ChannelHandlerContext, Channel, ChannelFuture, SocketAddress)
          Use Channels.connect(ChannelHandlerContext, ChannelFuture, SocketAddress) instead. Sends a "connect" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.disconnect(ChannelHandlerContext, Channel, ChannelFuture)
          Use Channels.disconnect(ChannelHandlerContext, ChannelFuture) instead. Sends a "disconnect" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireChannelBound(ChannelHandlerContext, Channel, SocketAddress)
          Use Channels.fireChannelBound(ChannelHandlerContext, SocketAddress) instead. Sends a "channelBound" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireChannelClosed(ChannelHandlerContext, Channel)
          Use Channels.fireChannelClosed(ChannelHandlerContext). Sends a "channelClosed" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireChannelConnected(ChannelHandlerContext, Channel, SocketAddress)
          Use Channels.fireChannelConnected(ChannelHandlerContext, SocketAddress) instead. Sends a "channelConnected" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireChannelDisconnected(ChannelHandlerContext, Channel)
          Use Channels.fireChannelDisconnected(ChannelHandlerContext) instead. Sends a "channelDisconnected" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireChannelInterestChanged(ChannelHandlerContext, Channel, int)
          Use Channels.fireChannelInterestChanged(ChannelHandlerContext) instead. Sends a "channelInterestChanged" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireChannelInterestChanged(Channel, int)
          Use Channels.fireChannelInterestChanged(Channel) instead. Sends a "channelInterestChanged" event to the first ChannelUpstreamHandler in the ChannelPipeline of the specified Channel. 
org.jboss.netty.channel.Channels.fireChannelOpen(ChannelHandlerContext, Channel)
          Use Channels.fireChannelOpen(ChannelHandlerContext) instead. Sends a "channelOpen" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext.

Please note that this method does not trigger a "childChannelOpen" event unlike Channels.fireChannelOpen(Channel) method. 

org.jboss.netty.channel.Channels.fireChannelUnbound(ChannelHandlerContext, Channel)
          Use Channels.fireChannelUnbound(ChannelHandlerContext) instead. Sends a "channelUnbound" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireExceptionCaught(ChannelHandlerContext, Channel, Throwable)
          Use Channels.fireExceptionCaught(ChannelHandlerContext, Throwable) instead. Sends a "exceptionCaught" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireMessageReceived(ChannelHandlerContext, Channel, Object)
          Use Channels.fireMessageReceived(ChannelHandlerContext, Object) instead. Sends a "messageReceived" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.fireMessageReceived(ChannelHandlerContext, Channel, Object, SocketAddress)
          Use Channels.fireMessageReceived(ChannelHandlerContext, Object, SocketAddress) instead. Sends a "messageReceived" event to the ChannelUpstreamHandler which is placed in the closest upstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.DefaultServerChannelConfig.getWriteTimeoutMillis()
          Use WriteTimeoutHandler instead. 
org.jboss.netty.channel.DefaultChannelConfig.getWriteTimeoutMillis()
          Use WriteTimeoutHandler instead. 
org.jboss.netty.channel.ChannelConfig.getWriteTimeoutMillis()
          Use WriteTimeoutHandler instead. Returns the write timeout of the channel in milliseconds. If a write operation is not completed within the write timeout, an IOException will be raised. If the Channel does not support write operation, this property is not used at all, and therefore will be ignored. 
org.jboss.netty.channel.socket.http.HttpTunnelingSocketChannelConfig.getWriteTimeoutMillis()
           
org.jboss.netty.channel.socket.nio.NioSocketChannelConfig.isReadWriteFair()
          This property has been replaced by the writeBufferHighWaterMark and writeBufferLowWaterMark. Returns true if and only if an I/O thread should do its effort to balance the ratio of read and write operations. Assuring the read-write fairness is sometimes necessary in a high speed network because a certain channel can spend too much time on flushing the large number of write requests not giving enough time for other channels to perform I/O. The default value is false. 
org.jboss.netty.channel.Channels.messageEvent(Channel, ChannelFuture, Object)
          Instantiate UpstreamMessageEvent or DownstreamMessageEvent directly instead. Creates a new MessageEvent 
org.jboss.netty.channel.Channels.messageEvent(Channel, ChannelFuture, Object, SocketAddress)
          Instantiate UpstreamMessageEvent or DownstreamMessageEvent directly instead. Creates a new MessageEvent 
org.jboss.netty.handler.codec.serialization.ObjectDecoderInputStream.readLine()
           
org.jboss.netty.channel.Channels.setInterestOps(ChannelHandlerContext, Channel, ChannelFuture, int)
          Use Channels.setInterestOps(ChannelHandlerContext, ChannelFuture, int) instead. Sends a "setInterestOps" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.socket.nio.NioSocketChannelConfig.setReadWriteFair(boolean)
          This property has been replaced by the writeBufferHighWaterMark and writeBufferLowWaterMark. Sets if an I/O thread should balance the ratio of read and write operations. Assuring the read-write fairness is sometimes necessary in a high speed network because a certain channel can spend too much time on flushing the large number of write requests not giving enough time for other channels to perform I/O. The default value is false. 
org.jboss.netty.channel.DefaultServerChannelConfig.setWriteTimeoutMillis(int)
          Use WriteTimeoutHandler instead. 
org.jboss.netty.channel.DefaultChannelConfig.setWriteTimeoutMillis(int)
          Use WriteTimeoutHandler instead. 
org.jboss.netty.channel.ChannelConfig.setWriteTimeoutMillis(int)
          Use WriteTimeoutHandler instead. Sets the write timeout of the channel in milliseconds. If a write operation is not completed within the write timeout, an IOException will be raised. If the Channel does not support write operation, this property is not used at all, and therefore will be ignored. 
org.jboss.netty.channel.socket.http.HttpTunnelingSocketChannelConfig.setWriteTimeoutMillis(int)
           
org.jboss.netty.channel.Channels.unbind(ChannelHandlerContext, Channel, ChannelFuture)
          Use Channels.unbind(ChannelHandlerContext, ChannelFuture) instead. Sends a "unbind" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.write(ChannelHandlerContext, Channel, ChannelFuture, Object)
          Use Channels.write(ChannelHandlerContext, ChannelFuture, Object) instead. Sends a "write" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
org.jboss.netty.channel.Channels.write(ChannelHandlerContext, Channel, ChannelFuture, Object, SocketAddress)
          Use Channels.write(ChannelHandlerContext, ChannelFuture, Object, SocketAddress) instead. Sends a "write" request to the ChannelDownstreamHandler which is placed in the closest downstream from the handler associated with the specified ChannelHandlerContext. 
 



Copyright © 2008-2009 JBoss, by Red Hat. All Rights Reserved.