r7 - 20 Dec 2007 - 22:04:58 - BeckyHYou are here: Wiki >

December 24 - AppLogic 2.4.7 is now available and is the latest production release!

RPL: Event Replicator

Latest Version: 1.0.1

	At a Glance
	Catalog	System
	Category	Switches
	User volumes	no
	Min. memory	64M
	OS	Linux
	Constraints	no
	Questions/Comments	Ask Forum

RPL is a replicator for events. It replicates http requests received on its input terminal to all its output terminals.

RPL sends any headers and documents received with the request to the outputs. RPL ignores the responses from the output requests, including possible failures to send the request. RPL always returns SUCCESS for recognized http requests on its input, without waiting for any of the outputs to respond. For requests that require a document to be returned, RPL returns an empty document.

RPL is intended for distributing fire-and-forget asynchronous notifications. (Future versions of RPL may have additional parameterization that modifies its behavior, incl. aggregating the responses from outputs and returning them on the input).

RPL can tolerate, and indeed expects under normal circumstances, any of its outputs being unconnected or non-responsive. Appliances connected to RPL's outputs may be stopped, on standby or non-responsive, without this affecting the operation and performance of RPL.

RPL can be cascaded by connecting other RPL instances to one or more of RPL's outputs.

Prior to AppLogic 2.1.1, RPL is in the proto catalog.

Boundary

Resources

Resource	Minimum	Maximum	Default
CPU	0.05	4	0.05
Memory	64 MB	128 MB	64 MB
Bandwidth	1 Mbps	1 Gbps	1 Mbps

Note: the amount of memory given to the appliance does not affect its throughput or performance significantly. The memory only controls the amount of request data that can be concurrently submitted through RPL. (note: verify and consider limiting the max amount of memory to some small amount, like 128M)

Terminals

name	dir	prot.	description
`in`	in	`http`	request input. Http requests received on this input are replicated and sent to all of the connected RPL outputs. RPL completes the request with success and, where appropriate, an empty document, regardless of the results of forwarded requests and without waiting for any responses from the outputs.
`out1-out8`	out	`http`	replication outputs. Requests received on the input terminal are replicated to each of the connected outputs; the results are ignored. Any and all of these outputs can be left unconnected; any of the outputs may have connected appliances that are not started and/or non-responsive.