Results
Loading...
| java.lang.Object | |
| ↳ | android.net.rtp.RtpStream |
 Known Direct Subclasses
|
RtpStream represents the base class of streams which send and receive network packets with media payloads over Real-time Transport Protocol (RTP).
Using this class requires
INTERNET permission.
| Constants | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| int | MODE_NORMAL | This mode indicates that the stream sends and receives packets at the same time. | |||||||||
| int | MODE_RECEIVE_ONLY | This mode indicates that the stream only receives packets. | |||||||||
| int | MODE_SEND_ONLY | This mode indicates that the stream only sends packets. | |||||||||
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Associates with a remote host.
| |||||||||||
Returns the network address of the local host.
| |||||||||||
Returns the network port of the local host.
| |||||||||||
Returns the current mode.
| |||||||||||
Returns the network address of the remote host or
null if the
stream is not associated. | |||||||||||
Returns the network port of the remote host or
-1 if the stream
is not associated. | |||||||||||
Returns
true if the stream is busy. | |||||||||||
Releases allocated resources.
| |||||||||||
Changes the current mode.
| |||||||||||
| Protected Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Invoked when the garbage collector has detected that this instance is no longer reachable.
| |||||||||||
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
From class
java.lang.Object
| |||||||||||
This mode indicates that the stream sends and receives packets at the same time. This is the initial mode for new streams.
This mode indicates that the stream only receives packets.
This mode indicates that the stream only sends packets.
Associates with a remote host. This defines the destination of the outgoing packets.
| address | The network address of the remote host. |
|---|---|
| port | The network port of the remote host. |
| IllegalArgumentException | if the address is not supported or the port is invalid. |
|---|---|
| IllegalStateException | if the stream is busy. |
Returns the network address of the local host.
Returns the network address of the remote host or null if the
stream is not associated.
Returns the network port of the remote host or -1 if the stream
is not associated.
Returns true if the stream is busy. In this case most of the
setter methods are disabled. This method is intended to be overridden
by subclasses.
Releases allocated resources. The stream becomes inoperable after calling this method.
| IllegalStateException | if the stream is busy. |
|---|
Changes the current mode. It must be one of MODE_NORMAL,
MODE_SEND_ONLY, and MODE_RECEIVE_ONLY.
| mode | The mode to change to. |
|---|
| IllegalArgumentException | if the mode is invalid. |
|---|---|
| IllegalStateException | if the stream is busy. |
Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.
Note that objects that override finalize are significantly more expensive than
objects that don't. Finalizers may be run a long time after the object is no longer
reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup.
Note also that finalizers are run on a single VM-wide finalizer thread,
so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary
for a class that has a native peer and needs to call a native method to destroy that peer.
Even then, it's better to provide an explicit close method (and implement
Closeable), and insist that callers manually dispose of instances. This
works well for something like files, but less well for something like a BigInteger
where typical calling code would have to deal with lots of temporaries. Unfortunately,
code that creates lots of temporaries is the worst kind of code from the point of view of
the single finalizer thread.
If you must use finalizers, consider at least providing your own
ReferenceQueue and having your own thread process that queue.
Unlike constructors, finalizers are not automatically chained. You are responsible for
calling super.finalize() yourself.
Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.
| Throwable |
|---|