Commit 90f9e31d authored by wwalkowski's avatar wwalkowski

Moving out of the way

parent 470c3f89

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.

package org.ocap;
import java.io.*;
/**
* This class provides system utility functions.
*
* @author Brent Foust
* @author Frank Sandoval
* @author Shigeaki Watanabe
*/
public final class OcapSystem
{
/**
* Do not use. This is to prevent a public constructor from being
* generated.
*/
private OcapSystem()
{
}
/**
* Called by the monitor application to inform the OCAP implementation
* that it is configuring and the boot process may resume after it
* calls the <code>monitorConfiguredSignal</code> method, see Section
* 20.2.2.3 Boot Process while connected to the cable network – CableCARD
* device present.
* <br>
* On invocation of this method, the APIs used for conformance testing,
* specifically, <code>org.ocap.test.OCAPTest</code> SHALL be initialized
* for use. This means that the implementation SHALL perform the
* following actions:
* <ul>
* <li>a. Open a socket for receiving UDP datagrams on a port, the value
* of which is specified in the <code>port</code> parameter passed to this
* method.</li>
* <li>b. Wait to receive a datagram that contains a string formatted
* thus: <code>ate:a.b.c.d:xxxx:ppp</code> (string may be null-terminated),
* where 'a.b.c.d' represents an IPv4 address, and 'xxxx' represents an
* IP port number, and 'ppp' represents protocol type ('TCP' for TCP/IP and
* 'UDP' for UDP/IP). Any received datagrams which do not contain a
* properly formatted payload string SHALL be ignored. Once a datagram
* with a properly formatted string has been received, the datagram
* socket SHALL be closed.</li>
* <li>c. Attempt to establish a TCP or UDP socket connection to the test system
* using the IPv4 address and port number obtained in b. The protocol type
* for the socket connection is specified by 'ppp' string in b. This connected
* socket SHALL be used solely to transmit and receive data originating
* from the <code>org.ocap.test.OCAPTest</code> APIs and SHALL NOT be
* accessible to applications through other APIs. The TCP or UDP socket
* connection shall have a timeout of 'infinite'. If this method
* does not complete within the specified timeout period, an
* <code>IOException</code> SHALL be thrown.</li>
* <li>d. Return control to the caller.</li>
* </ul>
* <br>
* If this method is called with both the <code>port</code> and
* <code>timeout</code> parameters set to 0, then the OCAP
* implementation SHALL not enable the conformance testing APIs, which
* SHALL just return silently, without performing any action.
* <br>
* If the monitor application does not call this method in the time
* specified in section 20.2.2.3 Boot Process while connected to the
* cable network - CableCARD device present, then the OCAP
* implementation SHALL behave the same as if this method had been called
* with 0 specified for both the <code>port</code> and <code>timeout</code>
* parameters.
* If the monitor application does not call this method in the time
* specified in section 20.2.2.3 Boot Process while connected to the
* cable network - CableCARD device present, then the implementation
* SHALL behave the same as if this method had been called with 0
* specified for both the <code>port</code> and <code>timeout</code>
* parameters.
*
* @param port the IP port number to listen for datagrams from the test
* system on.
*
* @param timeout the time, in seconds to allow for a communications
* channel to be established with the test system.
*
* @throws SecurityException if application does not have
* MonitorAppPermission("signal configured").
*
* @throws IOException if a communications channel cannot be established
* with the test system within the amount of time specified by the
* <code>timeout</code> parameter.
*/
public static void monitorConfiguringSignal(int port, int timeout)
throws IOException
{
}
/**
* Called by the Initial Monitor Application to inform the OCAP
* implementation it has completed its configuration process and
* that the boot processing may resume. It is recommended that
* the monitor call this method as soon as possible after the
* <code>monitorConfiguringSignal</code> method has been
* called.
*/ public static void monitorConfiguredSignal()
{
}
}
package org.ocap.application;
import org.dvb.application.AppID;
import org.dvb.application.AppsDatabaseFilter;
import java.util.Enumeration;
/**
* <em>AppFilter</em> provides a means of filtering AppIDs. As a
* subclass of {@link AppsDatabaseFilter}, the method {@link #accept}
* makes a <code>true</code>/<code>false</code> decision based on an AppID.
*
* <p>An AppFilter contains a list of zero or more {@link AppPattern}s. Each
* AppPattern has the attributes: <em>pattern</em>, <em>action</em>, and
* <em>priority</em>. <em>pattern</em> specifies a group of AppIDs with
* a pair of ranges for organization ID and application ID.
* <em>action</em> specifies an action assigned to the AppID group;
* either {@link AppPattern#ALLOW}, {@link AppPattern#DENY}, or {@link
* AppPattern#ASK}. <em>priority</em> specifies this AppPattern's
* position in the search order: the biggest number comes first.
* Applications can insert an AppPattern anywhere in the search
* order by using the priority attribute effectively
* (<code>AppFilter.add</code>). When two or more AppPatterns in an
* AppFilter have the same priority, the search order among them is
* undefined. It is not recommendable to use AppPatterns that have the
* same priority but different actions.
*
* <p>When <code>accept</code> is called, the given AppID is compared to
* the AppID group of each AppPattern in the search order until a match
* is found. Then, it returns <code>true</code> or <code>false</code>
* if the action of matching AppPattern is <code>ALLOW</code> or
* <code>DENY</code> respectively. If no match is found,
* <code>accept</code> returns <code>true</code>.
*
* <p>If the action of matching AppPattern is <code>ASK</code>, then
* AppFilter calls <code>AppFilterHandler.accept</code> for the final