IT. Expert System.

Android Reference

RtpStream


android.net.rtp

Class RtpStream

  • Direct Known Subclasses:
    AudioStream


    public class RtpStream
    extends Object
    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 android.Manifest.permission#INTERNET permission.

    • Field Summary

      Fields
      Modifier and Type Field and Description
      static int MODE_NORMAL
      This mode indicates that the stream sends and receives packets at the same time.
      static int MODE_RECEIVE_ONLY
      This mode indicates that the stream only receives packets.
      static int MODE_SEND_ONLY
      This mode indicates that the stream only sends packets.
    • Field Detail

      • MODE_NORMAL

        public static final int MODE_NORMAL
        This mode indicates that the stream sends and receives packets at the same time. This is the initial mode for new streams.
        See Also:
        Constant Field Values
      • MODE_SEND_ONLY

        public static final int MODE_SEND_ONLY
        This mode indicates that the stream only sends packets.
        See Also:
        Constant Field Values
      • MODE_RECEIVE_ONLY

        public static final int MODE_RECEIVE_ONLY
        This mode indicates that the stream only receives packets.
        See Also:
        Constant Field Values
    • Method Detail

      • getLocalAddress

        public InetAddress getLocalAddress()
        Returns the network address of the local host.
      • getLocalPort

        public int getLocalPort()
        Returns the network port of the local host.
      • getRemoteAddress

        public InetAddress getRemoteAddress()
        Returns the network address of the remote host or null if the stream is not associated.
      • getRemotePort

        public int getRemotePort()
        Returns the network port of the remote host or -1 if the stream is not associated.
      • isBusy

        public boolean isBusy()
        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.
      • getMode

        public int getMode()
        Returns the current mode.
      • associate

        public void associate(InetAddress address,
                     int port)
        Associates with a remote host. This defines the destination of the outgoing packets.
        Parameters:
        address - The network address of the remote host.
        port - The network port of the remote host.
        Throws:
        IllegalArgumentException - if the address is not supported or the port is invalid.
        IllegalStateException - if the stream is busy.
        See Also:
        isBusy()
      • release

        public void release()
        Releases allocated resources. The stream becomes inoperable after calling this method.
        Throws:
        IllegalStateException - if the stream is busy.
        See Also:
        isBusy()
      • finalize

        protected void finalize()
                         throws Throwable
        Description copied from class: Object
        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.

        Overrides:
        finalize in class Object
        Throws:
        Throwable


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

License.
All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 3358 / . Delta: 0.02656 с