| Home >> All >> com >> voytechs |
| | com.voytechs.example.* (6) | | com.voytechs.html.* (55) | | com.voytechs.jnetanalyzer.* (25) |
| | com.voytechs.jnetstream.* (151) | | com.voytechs.util.* (1) |
Package Samples:
com.voytechs.jnetanalyzer.message.swing: Abstract representation of message being analyzed between endpoints.
com.voytechs.jnetanalyzer.tcp.swing: Analyzes and keeps states about TCP connections.
com.voytechs.jnetstream.primitive.address: JNetStream primitive (datatypes) objects.
com.voytechs.example.desktop
com.voytechs.example.helloworld
com.voytechs.html.application
com.voytechs.html.component.extended
com.voytechs.html.component
com.voytechs.html.event
com.voytechs.html.io
com.voytechs.html.util
com.voytechs.jnetanalyzer.message
com.voytechs.jnetanalyzer.tcp
com.voytechs.jnetstream.codec
com.voytechs.jnetstream.io
com.voytechs.jnetstream.npl
com.voytechs.jnetstream.primitive
com.voytechs.jnetstream.protocol.layer2
com.voytechs.jnetstream.protocol.layer3
com.voytechs.jnetstream.protocol.layer4
Classes:
ExpressionParser: Express parser. A standard C-Like expression will be parsed into an expression tree. The expression tree then can be traversed and evaluated via a number of methods. The expression parser is called using the parseExpression() method and passing it a String containing the expression to be parsed. The parser has the following operators defined: "+" - class PlusOpNode - NORMAL/BINARY "-" - class MinusOpNode - NORMAL/BINARY "*" - class MultiplyOpNode - HIGH/BINARY "/" - class DivideOpNode - HIGH/BINARY "&" - class AndOpNode - HIGH/BINARY "|" - class OrOpNode - HIGH/BINARY "%" - class ModOpNode - NORMAL/BINARY ...
HelloWorldServlet: This is a sample application which simply displays HelloWorld message back to the client browser. Here is how we write this application. subclass the ToolServlet class and define its abstract method createSessionPanel. In the method createSessionPanel() we create a new panel, add a Text("Hello World!!!") object and return it. To install this application in your servlet environment, for tomcat we do the following. We have to define the new servlet in web.xml file and copy the files to the appropriate tomcat directory. We add to WEB-INF/web.xml file: HelloWorld com.voytechs.example.helloworld.HelloWorldServlet ...
PacketInputStream: Stream object that reads either an InputStream of bytes and allows access to the byte stream with the following features: 1) data can be read in either bytes or individual bits. 2) position within the stream can be pushed on to a stack 3) position can be poped off of the stack. 4) a packet structure is imposed on the stream so that you can query or be notified when the end of an individual packet byte stream is over and when the next packet byte stream is beginning. 5) data can be read in any binary format (Big Endian or Little Endian) 6) Packet capture information is accessable, such as: a) IP ...
PcapInputStream: Structure of TCPDump file. struct pcap_file_header { bpf_u_int32 magic; u_short version_major; u_short version_minor; bpf_int32 thiszone; // gmt to local correction // bpf_u_int32 sigfigs; // accuracy of timestamps // bpf_u_int32 snaplen; // max length saved portion of each pkt // bpf_u_int32 linktype; // data link type (LINKTYPE_*) // }; Now per each packet: struct pcap_pkthdr { struct timeval ts; // time stamp // bpf_u_int32 caplen; // length of portion present // bpf_u_int32 len; // length this packet (off wire) // };
HtmlWriter: Html Print Writer. Will output HTML primitives on the supplied outputstream. Because Http protocol allows binary output to the stream as long as the appropriate MIME header is supplied, this object also allows access to the underlying output stream so binary data can be output as well if needed (getOutputStream()); This writer supplies all of the basic HTML 4.0 tags. It also supplies some convenience functions. 3 types of HTML tag methods exist. *Start() and *End() mentods. ie. formStart() & formEnd() Convenience functions that supply both start and end tags. ie form(String formBody) Tags that ...
AbstractMessageListener: Convenience class that defines blank method for MessageListener interface. Message Listener interface is intended to notify listeners of various Message based events. A Message is made up of sequence of segments all of which combine into a single entity called a message. At IP layer a message is the entire IP Dgram after all of the IP fragmeents have been reassmebled and each IP fragment is a message segement. At TCP layer is made up of 2 messages, 1 for each stream in each direction. The entire stream is considered a message. Each TCP segment is a message segment from the beginning until the last ...
MessageListener: Message Listener interface is intended to notify listeners of various Message based events. A Message is made up of sequence of segments all of which combine into a single entity called a message. At IP layer a message is the entire IP Dgram after all of the IP fragmeents have been reassmebled and each IP fragment is a message segement. At TCP layer is made up of 2 messages, 1 for each stream in each direction. The entire stream is considered a message. Each TCP segment is a message segment from the beginning until the last segment arrives and TCP stream is closed.
LoginPanel: A two state button. When no user is logged in the default login button displayes 'Login' text. By clicking on the Login element, a Login popup is displayed on the client. After a user has logged in, this element automatically turns off the login button and displays its second button, the profile button. This has the effect of at first seeing a Login then a Profile button immediately after the login. The displayed simple elements can be replaced by using the addLoginElement() and addProfileElement() methods.
IpAddress: A Class for storing IP Addresses Currently is only designed to utilize IPv4 (32bit) addresses. Class also contains utility methods for DNS lookups. There are various functions for converting the IP address to a LONG. Why would you want to use a long for storage of an IP address, in my case I store IP address in a database as an UNSIGNED INT, java does not have unsigned numbers so you have to go to next bigger primitive type to store it or do like other implementations do store the address in a byte array.
IpNumber: A Class for storing IP Addresses Currently is only designed to utilize IPv4 (32bit) byteArrayAddresses. There are various functions for converting the IP byteArrayAddress to a LONG. Why would you want to use a long for storage of an IP byteArrayAddress, in my case I store IP byteArrayAddress in a database as an UNSIGNED INT, java does not have unsigned numbers so you have to go to next bigger primitive type to store it or do like other implementations do store the byteArrayAddress in a byte array.
ToolServlet: Base class for all tool servlets. One ToolServlet object exists and it manages individual ToolSession objects. One ToolSession object exists per each user session as created by the WebServer/WebBrowser. Tool servlets interact with each other in a way that allows commnitcation between any tools servlet and discoveries of tools by any of the tools. (ie. A desktop tool can discover all other tools and ask them to produce content that can be pluged into the desktop.)
Address: A Class for storing IP Addresses Currently is only designed to utilize IPv4 (32bit) addresses. There are various functions for converting the IP address to a LONG. Why would you want to use a long for storage of an IP address, in my case I store IP address in a database as an UNSIGNED INT, java does not have unsigned numbers so you have to go to next bigger primitive type to store it or do like other implementations do store the address in a byte array.
ArrayDimensionNode: Support class that allows muti-dimensional array manipulation. Since array references can have dynamic code associated with array lookup, a number of convenience functions are performed by the class. 1) Bounds checking for MAX and MIN bounds for all dimensions. 2) Node traversal for each dimension 3) Scalar array size computation which also needs to be done at run time because of dynamic code.
Container: A generic container object is a component that can contain other components. Components added to a container are tracked in a list. The order of the list will define the components' front-to-back stacking order within the container. If no index is specified when adding a component to a container, it will be added to the end of the list (and hence to the bottom of the stacking order).
TableContainer: A generic container object is a component that can contain other components. Components added to a container are tracked in a list. The order of the list will define the components' front-to-back stacking order within the container. If no index is specified when adding a component to a container, it will be added to the end of the list (and hence to the bottom of the stacking order).
ServletFrame: A ServletFrame object is a adaptor for Servlets. Lets a servlet initialize the top level frame using servlet specific parameters. Lower level objects do not know that servlet is actually controlling the HTML output. Also additional HTML specific functions such as HTTP MIME headers and other servlet specific or servlet bound resources are defined by overriding lower level object methods.
DispatcherBroker: Specialized container object for holding dispatcher listeners. Because of dynamic binding of HTML components and the dispatcher, addtion of listeners has to be delayed until the dispatcher bound and initlizated otherwise the binding can't occur. This object adapts to the HTML component special requirements such as generating a URL acceptable parameters or HTML Form tags.
HtmlDispatcherBroker: Specialized container object for holding dispatcher listeners. Because of dynamic binding of HTML components and the dispatcher, addtion of listeners has to be delayed until the dispatcher bound and initlizated otherwise the binding can't occur. This object adapts to the HTML component special requirements such as generating a URL acceptable parameters or HTML Form tags.
FilterDecoder: Decoder which allows filtering on packets as they are proccessed. Appropriate filters can be defined and are immediately applied and checked as packet input stream is being decoded. Minimum amount of data is decoded until a filter hit is achieved. Appropriate permit or deny action is taken. In deny case, the packet processing is stopped with no further processing.
Dispatcher: An event dispatcher object. A user action triggers an event to be generated. Events are dispatched to event listeners. This is an abstract class and an appropriate implementation of it should be created, such as ServletDispatcher or CGI Dispatcher with appropriate hooks for processing the event conditions in whatever form they may be (ie. http forms).
JMessage: JMessage is a rectangular representation of a network message. The message is made up of many segmenets. As segments are added they are displayed within the message box. Appropriate colors and labels can be assigned to each segements and entire message. Message contains scrollbars if it doesn't fit on the screen.
MessageListenerSupport: Handles the lists and dispatching of events to listeners. This class is a support class for Message based event handling. Events can be sent on behalf of a message or its individual segments. In addition standard listner interface methods for notification of new message or its segments are implemented.
ProtocolDataInputStream: This stream object extends the DataInputStream which defines how to read basic data types from a binary stream. This stream in addition to the Java native primitives that DataInput defines, add ability to read on a variable bit boundry. Any subset of bits can be read and returned in 'int' data type.
Header: Protocol Header definition interface. This interface allows access to get various properties of a created run-time instance of header object. This object is created based on the HeaderFactory definition object which contains various global and instance specific parameters.
JMessageControlBox: Control area in a message box. Control area has the following sub-areas defined. 1) Scalable text label 1-3 = labels in upper left hand corner. 2) Expansion/Collapse button in lower left corcer. 3) lights 1-3 = lights that can be set to any color in upper right corner.
| Home | Contact Us | Privacy Policy | Terms of Service |