public abstract class XMPPInputOutputStream
extends java.lang.Object
| Modifier and Type | Class and Description |
|---|---|
static class |
XMPPInputOutputStream.FlushBehavior |
| Modifier and Type | Field and Description |
|---|---|
protected java.lang.String |
compressionMethod |
protected static XMPPInputOutputStream.FlushBehavior |
flushBehavior |
| Modifier | Constructor and Description |
|---|---|
protected |
XMPPInputOutputStream(java.lang.String compressionMethod) |
| Modifier and Type | Method and Description |
|---|---|
java.lang.String |
getCompressionMethod() |
abstract java.io.InputStream |
getInputStream(java.io.InputStream inputStream) |
abstract ExtendedOutputStream |
getOutputStream(ExtendedOutputStream outputStream) |
abstract boolean |
isSupported() |
static void |
setFlushBehavior(XMPPInputOutputStream.FlushBehavior flushBehavior)
Set the flush behavior.
|
protected static XMPPInputOutputStream.FlushBehavior flushBehavior
protected final java.lang.String compressionMethod
protected XMPPInputOutputStream(java.lang.String compressionMethod)
public static void setFlushBehavior(XMPPInputOutputStream.FlushBehavior flushBehavior)
XMPPInputOutputStream.FlushBehavior.FULL_FLUSH which may not achieve
the best compression ratio, but provides better security against certain attacks. Only use
XMPPInputOutputStream.FlushBehavior.SYNC_FLUSH if you fully understand the implications.
The experimental XMPPInputOutputStream.FlushBehavior.ON_CHANNEL_CHANGE theoretically provides the best
trade off between efficiency and security. But the feature is not well tested and doesn't
work with all compression implementations.
flushBehavior - public java.lang.String getCompressionMethod()
public abstract boolean isSupported()
public abstract java.io.InputStream getInputStream(java.io.InputStream inputStream)
throws java.io.IOException
java.io.IOExceptionpublic abstract ExtendedOutputStream getOutputStream(ExtendedOutputStream outputStream) throws java.io.IOException
java.io.IOException