Home >> All

•	juju.reattore.* (91)

Package Samples:

• juju.reattore.perfcap.var: Automated performance testing and capture tool.  
• juju.reattore.loadtest.controller: Automated HTTP load test tool.  
• juju.reattore.util: Single threaded HTTP server.  
• juju.reattore.io.impl: Reattore IO package.  
• juju.reattore.core.reactor.impl
• juju.reattore.core.reactor
• juju.reattore.core.rr
• juju.reattore.io
• juju.reattore.loadtest.controller.impl
• juju.reattore.loadtest
• juju.reattore.perfcap.reporter.impl
• juju.reattore.perfcap.reporter
• juju.reattore.perfcap.tester.impl
• juju.reattore.perfcap.tester
• juju.reattore.perfcap.var.impl
• juju.reattore.perfcap
• juju.reattore.protocol.http.impl
• juju.reattore.protocol.http
• juju.reattore.server.http
• juju.reattore.server.intercept.impl

Classes:

• PartitioningInterceptor: Interceptor that hands off to a different child interceptor based on the original request. Can be used to re-map directories or to add servlets. Top down only. Does not handle conflicts. Examples: add('/foo/', ...) - hand off /foo/ and below. add('/~', ...) - user dir like, hand off ~ and below. /foo/bar.html - sub request for bar.html ~michaelh/bar.html - sub request for michaelh/bar.html
• VelocityReporter: Generates an arbitrary report using a user defined Velocity template. The available variables are: root - Top level of a tree of Maps containing all of the results. The map is indexed by variable name. names - List of all of the variable names in order. values - List of Lists of all of the values a variable took in order received.
• Interceptor: An Interceptor is a module that is given a chance to process an incomming request and to respond to it. The Interceptor can do any combination of passing the request on, causing a side effect on the response such as adding a header, or supply the response body.
• ByteSourceSink: Buffer that may be used for temporary storage and which is backed by a byte array. Used for storing an incomming stream for later use. Concurrent read/write access is unpredictable. Concurrent read access shares the same stream position and marks.
• ErrorInterceptor: Interceptor that serves an error document if the main path can't find anything. The main path will be given the first chance to handle the request. If the main path cannot then the error path is given a chance.
• CSVReporter: Writes a report to a CSV file. The first line is a header containing the names of all of the independant variables, followed by the name of the result point. The following lines are the samples in order.
• CachableInterceptor: An interceptor that generates results that can be cached. An interceptor higher in the tree may cache the response body if the response succeeds. The body must implement CachableSource.
• Reactor: Base interface for any channel 'Reactors'. A reactor is a system that manages many event producers within one thread, handing off the events to the event handlers as required.
• Tester: A bean that can be setup and can run a test. Each independant variable will be applied to this tester before running. The tester will be re-used for each test.
• CSVTester: 'Tests' using previously recorded data. This tester can import data previously recorded using the CSVReporter including de-serialising the recorded results.
• BaseHttpRequest: HTTP request implementation. Wraps a HTTP parser and provides the request access methods. Also acts as a proxy, only resolving certain fields as required.
• GaugeStat: Statistic module that manages a gauge. A gauge is a statistic that has a current value that goes up and down, such as the number of connections.
• ServerSocketReactor: A reactor that understands server sockets and will handle new incoming connections and will hand them off to the handler as they arrive.
• Controller: A controller is the central point in a load test. The controller takes a URL chooser and a reactor and handles running the load test.
• HttpRequest: Encapsulates a HTTP request. Note that a URL is basically of the format protocol://[auth:]host/path[?query]
• Sink: A sink is a system that will accept data and store it. This data can normally be accessed through the corresponding source later.
• Chooser: A chooser takes a set of URLs and provides them to the controller on request. A chooser could be round robin, random, etc.
• ChannelFileSource: A byte source that serves from a file using channels. Implemented by reading the whole file into a byte buffer.
• HttpMediator: The mediator acts as a central point allowing the server and client handlers to avoid knowing about each other.
• ClientSocketHandler: Callback interface related to a client socket channel. Called by the reactor when the socket state changes.
• Base64: Provides encoding of raw bytes to base64-encoded characters, and decoding of base64 characters to raw bytes.
• Reattore: Main entry point for the HTTP server. Creates the server tree from a configuration file and runs it.
• HttpProtocol: Encapsulates the logic and processing of a HTTP session, including any protocol responses. Stateful.
• StatInterceptor: Very simple statistics servlet. Adds 'stat' to the velocty context, which is a list of Stat objects.
• Reporter: A module that takes the variables used and results generated from a test and turns it into a report.

Home | Contact Us | Privacy Policy | Terms of Service