Free serial ws keygens software for linux

Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget.

SYNOPSIS

use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}

This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.

The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.

iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".

Openwsman is a project intended to provide an open-source implementation of the Web Services Management specification and to expose system management information on the Linux operating system using the WS-Management protocol.
WS-Management is based on a suite of web services specifications and usage requirements that exposes a set of operations focused on and covers all system management aspects.
This specification identifies a core set of Web service specifications and usage requirements to expose a common set of operations that are central to all systems management. This comprises the abilities to:
- Discover the presence of management resources and navigate between them
Get, Put, Create, Rename, and Delete individual management resources, such as settings and dynamic values
- Enumerate the contents of containers and collections, such as large tables and logs
- Subscribe to events emitted by managed resources
- Execute specific management methods with strongly typed input and output parameters
Enhancements:
- fixed client bug: return 0 if no auth callback is defined

Bio::SAGE::Comparison module compares data from serial analysis of gene expression (SAGE) libraries.

SYNOPSIS

use Bio::SAGE::Comparison;
$sage = Bio::SAGE::Comparison->new();

This module provides several tools for comparing data generated from serial analysis of gene expression (SAGE) libraries.

BACKGROUND

Serial analysis of gene expression (SAGE) is a molecular technique for generating a near-global snapshot of a cell population’s transcriptome. Briefly, the technique extracts short sequences at defined positions of transcribed mRNA. These short sequences are then paired to form ditags. The ditags are concatamerized to form long sequences that are then cloned. The cloned DNA is then sequenced. Bioinformatic techniques are then employed to determine the original short tag sequences, and to derive their progenitor mRNA. The number of times a particular tag is observed can be used to quantitate the amount of a particular transcript. The original technique was described by Velculescu et al. (1995) and utilized an ~14bp sequence tag. A modified protocol was introduced by Saha et al. (2002) that produced ~21bp tags.

PURPOSE

This module facilitates the comparison of SAGE libraries. Specifically:

1. Calculations for determining the statistical
significance of expression differences.
2. Dynamically convert longer-tag libraries to
a shorter type for comparison (e.g. comparing
a LongSAGE vs. a regular SAGE library).

Both regular SAGE (14mer tag) and LongSAGE (21mer tag) are supported by this module.

Statistical significance in library comparisons is calculated using the method described by Audic and Claverie (1997). Code was generated by directly porting the authors original C source.

Plasmatronics Perl module is a Plasmatronics PL regulator controller.

SYNOPSIS

use Device::Regulator::Plasmatronic;
my $r = Device::Regulator::Plasmatronic;
print "Current state of charge = " . $r->pl_dsoc . "n";

This is an interface library via the serial port to a Plasmatronics Regulator. (http://www.plasmatronics.com.au/)

MAJOR LIMITATIONS

Serial Port

I have to replace the serial port driver - currently I use the unix only version, but I have written

Hard Coded Multiplier

The multiplier used for voltages etc is hard coded (currently 4 = 48 Volt system). This can be read from the system, so I will have to do that as part of the initialisation.

Combined Values

Load and other things combine values from multiple locations to allow for larger numbers. I know that I have got this wrong in a number of places. Work to be done to test these for large numbers (eg: > 25 Amps etc).

Apache Synapse is a mediation framework for Web Services. Synapse allows messages flowing through, into, or out of an organization to be mediated. Synapse, incidentally, is pronounced "sine-apse", and not "sin-apse".
Main features:
- A streamlined configuration model and a new XML syntax
- Proxy Services (service mediation) and Message mediation
- Concept of Endpoints
- Integration of a Registry and dynamic refresh of resources as well as rules used to mediate
- Support for http and JMS transports
- Support for WS-Reliable Messaging and WS-Security through WS-Policies
- Script mediator supporting all BSF scripting languages
- Support for error handling and recovery
- Support for WS-RM sequences
- Many built in mediators
- Maven 2 based build process
- Many samples and a built-in Axis2 server to try out and experiment with samples (Samples includes WS-Security, JMS POX/Text messages, Script mediation and many more samples which can be run out of the box)
- Enhanced documentation
Enhancements:
- Significant improvements including non-blocking HTTP and HTTPS transports, better samples, and better documentation.

Whitespace is a Perl module to cleanup various types of bogus whitespace in source files.

SYNOPSIS

use Whitespace;

# Instantiate a whitespace object with
# both input and output files specified
$ws = new Whitespace($infile, $outfile);

# Instantiate a whitespace object with
# only the input files specified (in-place cleanup)
$ws2 = new Whitespace($infile);

# Detect the whitespaces
$ret = $ws->detect();

detect returns undef if it is unable to operate on the given file.

The error that caused the undef can be retrieved using error

print $ws->error() . "n" unless defined $ret;

detect returns the types of whitespaces detected as a hash which can be retrieved using the method status. The populated hash might look like this, if the file only had leading, trailing and end-of-line spaces (say on 3 lines).

%stat = %{$env->status()};
print map "$_ => $stat{$_}n", sort keys %stat;

eol => 3
indent => 0
leading => 1
spacetab => 0
trailing => 1

Cleanup can be achieved for all the whitespaces or for just a given type of whitespace, using the following methods.

If a outfile is given, the cleaned contents are written to this file. If not, the contents are replaced in-place. undef is returned if there was an error writing the file.

# To cleanup the all the whitespaces
$ret = $env->cleanup();

# To cleanup leading whitespaces only
$leadstat = $env->leadclean();

# To cleanup trailing whitespaces only
$trailstat = $env->trailclean();

# To cleanup indentation whitespaces only
$indentstat = $env->indentclean();

# To cleanup space-followed-by-tabs only
$sftstat = $env->spacetabclean();

# To cleanup end-of-line whitespaces only
$eolstat = $env->eolclean();

GNU BPEL2oWFN project translates a web service expressed in WS-BPEL (Web Service Business Process Execution Language) into an oWFN (open Workflow Net). This oWFN can be used to:
- check for controllability or generate the operating guideline using the tool Fiona,
- check for deadlocks or any other Petri net property, or
- check any temporal logic formula with a variety of model checking tools.
GNU BPEL2oWFN uses static analysis to make the generated Petri net model as compact as possible to analyze a chosen property. This is called flexible model generation. Furthermore, several design flaws can be detected using control and data flow analysis.