java.lang.Object
com.prolifics.servlet.Comm
- class Comm
- extends java.lang.Object
test servlet. This servlet simply echos back the request line and
headers that were sent by the client, plus any HTTPS information
which is accessible.
- Version:
- @(#)Comm.java 77.1 99/04/22 15:03:03
|
Constructor Summary |
Comm()
|
sccsid
private static java.lang.String sccsid
in
private java.io.InputStream in
out
private java.io.OutputStream out
fd
private int fd
sock
private java.net.Socket sock
Comm
public Comm()
main
public static void main(java.lang.String[] args)
throws java.io.IOException
nopen
private int nopen(byte[] name,
int fd)
throws java.io.IOException
nclose
private void nclose(int fd)
throws java.io.IOException
ninit
private static void ninit()
ngetindex
private static int ngetindex()
nfreeindex
private static void nfreeindex(int index)
destroy
public void destroy()
finalize
protected void finalize()
throws java.lang.Throwable
- Description copied from class:
java.lang.Object
- Called on an object by the Virtual Machine at most once,
at some point after the Object is determined unreachable
but before it is destroyed. You would think that this
means it eventually is called on every Object, but this is
not necessarily the case. If execution terminates
abnormally, garbage collection does not always happen.
Thus you cannot rely on this method to always work.
For finer control over garbage collection, use references
from the
java.lang.ref package.
Virtual Machines are free to not call this method if
they can determine that it does nothing important; for
example, if your class extends Object and overrides
finalize to do simply super.finalize().
finalize() will be called by a java.lang.Thread that has no
locks on any Objects, and may be called concurrently.
There are no guarantees on the order in which multiple
objects are finalized. This means that finalize() is
usually unsuited for performing actions that must be
thread-safe, and that your implementation must be
use defensive programming if it is to always work.
If an Exception is thrown from finalize() during garbage
collection, it will be patently ignored and the Object will
still be destroyed.
It is allowed, although not typical, for user code to call
finalize() directly. User invocation does not affect whether
automatic invocation will occur. It is also permitted,
although not recommended, for a finalize() method to "revive"
an object by making it reachable from normal code again.
Unlike constructors, finalize() does not get called
for an object's superclass unless the implementation
specifically calls super.finalize().
The default implementation does nothing.
stringToBytes
public static byte[] stringToBytes(java.lang.String src)
bytesToString
public static java.lang.String bytesToString(byte[] src,
int offset,
int len)
open
public void open(java.lang.String name,
java.lang.String URL)
throws java.io.IOException
ngetArchitecture
private static int ngetArchitecture()
ngetDispatcherPort
private int ngetDispatcherPort(byte[] name)
throws java.io.IOException
ngetInitialReadSize
private int ngetInitialReadSize()
throws java.io.IOException
nprepareRequest
private int nprepareRequest(byte[] buf,
byte[] name,
byte[] URL,
int fd)
ngetLengthToRead
private int ngetLengthToRead(byte[] buf)
throws java.io.IOException
ngetServerPort
private int ngetServerPort(byte[] buf)
throws java.io.IOException
oldopen
public void oldopen(java.lang.String name,
java.lang.String URL)
throws java.io.IOException
close
public void close()
throws java.io.IOException
getInputStream
public java.io.InputStream getInputStream()
throws java.io.IOException
getOutputStream
public java.io.OutputStream getOutputStream()
throws java.io.IOException
JAVADOC | 
SOURCE | 
DOWNLOAD | NESTED | FIELD | CONSTR | METHOD