Free hspd 8 software for linux

hatatap project is an HTTP scripting tool with scripts in XML. The scripts are transformed into Java/o:XML before they are either executed from the commandline, integrated into Ant build files, or run interactively from a Web application.
hatatap supports cookies, Javascript, HTML DOM, Web Services/SOAP, performance tests with concurrency, test reports, regular expression matching, and stateful Web site navigation. It is written in o:XML and uses HttpUnit.
Main features:
- stateful navigation
- HTML forms
- nested frames
- pop-up windows
- cookies and headers
- GET, POST and PUT requests
- HTTPS support
- regular expressions
- DOM-based response navigation using XPath
- XML requests and responses (eg SOAP) for testing web services
- multipart forms and file uploads
- multipart MIME XML requests
- millisecond timings and concurrency for performance testing
- XML test results
- random value functions
- extensible test scripts
- JavaScript support
- basic HTTP authentication
- HTTP proxy settings with authentication
- automatic redirect and refresh
- SSL certificate management
- domain name aliasing
- multipart MIME server responses (todo)
Enhancements:
- Binary attachment capabilities were added.
- A classpath problem was fixed in the Ant task.
- An upgrade was made to HttpUnit 1.6.2 and the latest ObjectBox and o:Lib releases.

AutoSplit is a Perl module that can split a package for autoloading.

SYNOPSIS

autosplit($file, $dir, $keep, $check, $modtime);

autosplit_lib_modules(@modules);

This function will split up your program into files that the AutoLoader module can handle. It is used by both the standard perl libraries and by the MakeMaker utility, to automatically configure libraries for autoloading.

The autosplit interface splits the specified file into a hierarchy rooted at the directory $dir. It creates directories as needed to reflect class hierarchy, and creates the file autosplit.ix. This file acts as both forward declaration of all package routines, and as timestamp for the last update of the hierarchy.
The remaining three arguments to autosplit govern other options to the autosplitter.

$keep

If the third argument, $keep, is false, then any pre-existing *.al files in the autoload directory are removed if they are no longer part of the module (obsoleted functions). $keep defaults to 0.

$check

The fourth argument, $check, instructs autosplit to check the module currently being split to ensure that it includes a use specification for the AutoLoader module, and skips the module if AutoLoader is not detected. $check defaults to 1.

$modtime

Lastly, the $modtime argument specifies that autosplit is to check the modification time of the module against that of the autosplit.ix file, and only split the module if it is newer. $modtime defaults to 1.

Typical use of AutoSplit in the perl MakeMaker utility is via the command-line with:

perl -e use AutoSplit; autosplit($ARGV[0], $ARGV[1], 0, 1, 1)

Defined as a Make macro, it is invoked with file and directory arguments; autosplit will split the specified file into the specified directory and delete obsolete .al files, after checking first that the module does use the AutoLoader, and ensuring that the module is not already currently split in its current form (the modtime test).

The autosplit_lib_modules form is used in the building of perl. It takes as input a list of files (modules) that are assumed to reside in a directory lib relative to the current directory. Each file is sent to the autosplitter one at a time, to be split into the directory lib/auto.

In both usages of the autosplitter, only subroutines defined following the perl __END__ token are split out into separate files. Some routines may be placed prior to this marker to force their immediate loading and parsing.

Multiple packages

As of version 1.01 of the AutoSplit module it is possible to have multiple packages within a single file. Both of the following cases are supported:

package NAME;
__END__
sub AAA { ... }
package NAME::option1;
sub BBB { ... }
package NAME::option2;
sub BBB { ... }

package NAME;
__END__
sub AAA { ... }
sub NAME::option1::BBB { ... }
sub NAME::option2::BBB { ... }

Perl is a stable, cross platform programming language. Perl project is used for mission critical projects in the public and private sectors and is widely used to program web applications of all needs.
Main features:
- Perl is a stable, cross platform programming language.
- It is used for mission critical projects in the public and private sectors.
- Perl is Open Source software, licensed under its Artistic License, or the GNU General Public License.
- Perl was created by Larry Wall.
- Perl 1.0 was released to usenets alt.comp.sources in 1987
- PC Magazine named Perl a finalist for its 1998 Technical Excellence Award in the Development Tool category.
- Perl is listed in the Oxford English Dictionary.
- Perl takes the best features from other languages, such as C, awk, sed, sh, and BASIC, among others.
- Perls database integration interface (DBI) supports third-party databases including Oracle, Sybase, Postgres, MySQL and others.
- Perl works with HTML, XML, and other mark-up languages.
- Perl supports Unicode.
- Perl is Y2K compliant.
- Perl supports both procedural and object-oriented programming.
- Perl interfaces with external C/C++ libraries through XS or SWIG.
- Perl is extensible. There are over 500 third party modules available from the Comprehensive Perl Archive Network (CPAN).
- The Perl interpreter can be embedded into other systems.
- Perl is the most popular web programming language due to its text manipulation capabilities and rapid development cycle.
- Perl is widely known as "the duct-tape of the Internet".
- Perls CGI.pm module, part of Perls standard distribution, makes handling HTML forms simple.
- Perl can handle encrypted Web data, including e-commerce transactions.
- Perl can be embedded into web servers to speed up processing by as much as 2000%.
- mod_perl allows the Apache web server to embed a Perl interpreter.
- Perls DBI package makes web-database integration easy.

XMMS 1.2.8 brings you a powerful tool which is the most widely known media player for UNIX systems. Basically a WinAMP clone, but a really good one. It's very easy to use this software. Download to enjoy it now.

buzhug is a fast, pure-Python database engine, using a syntax that Python programmers should find very intuitive.
The data is stored and accessed on disk (it is not an in-memory database) ; the implementation has been designed to make all operations, and especially selection, as fast as possible with an interpreted language.
The database is implemented as a Python iterator, yielding objects whose attributes are the fields defined when the base is created ; therefore, requests can be expressed as list comprehensions or generator expressions, instead of SQL queries :
for record in [ r for r in db if r.name == pierre ]
print record.name,record.age
instead of
cursor.execute("SELECT * IN db WHERE name = pierre")
for r in cursor.fetchall():
print r[0],r[1]
List comprehension is only one of the different ways to select records ; direct access by record identifier is almost immediate regardless of the size of the base, and the algorithms used in the select() method make selections extremely fast in most cases.
buzhug supports concurrency control by versioning, cleanup of unused data when many records have been deleted, easy links between bases, adding and removing fields on an existing base, etc.
Database speed comparisons are not easy to make. I made a limited benchmark using the same use cases as SQLites author ; it shows that buzhug is much faster than other pure-Python modules (KirbyBase, gadfly) ; SQLite, which is implemented in C, is faster, but only less than 3 times on the average.
buzhug is an Open Source software, published under the revised BSD licence.
Enhancements:
- Small bug fix in links between bases

WMcp is a simple dockable pager for use in Window Maker.

Installation:

Unzip the file: gunzip wmcp-1.2.8.tar.gz
Untar the file: tar xvf wmcp-1.2.8.tar
CD to src dir: cd wmcp-1.2.8

do one of these makes:

make -- make wmcp using the default button scheme (scalpel)
make scalpel -- make wmcp using the scalpel style button colors
make gv -- make wmcp using the ghostview style button colors

copy wmcp to some directory in your $PATH.
( ie: cp wmcp /usr/local/bin )

type wmcp

Grab the appicon and move it to the dock.

If make doesnt work, you may need to fiddle with the settings in the Makefile.

Tested on:

WindowMaker-0.20.3
WindowMaker-0.50.2
X Clients: Red Hat 5.0, Red Hat 6.0, HP-UX 10.20
X Servers: XFree86, Exceed, AccelX

Usage:

usage: wmcp [-g geometry] [-d dpy] [-n workspaces] [-a alt key] [-v]
[-c] [-w i/n/w] [-s y/n] [-x #] [-y #] [-h]

-g geometry: ie: 64x64+10+10
-d dpy: Display. ie: 127.0.0.1:0.0
-n workspaces: How many buttons to start with.
-a alt key: integer 1-4 defining ModXMask (default 1 Mod1Mask).
-w i/n/w: Window State: Iconic, Normal, Withdrawn (default Withdrawn)
-s y/n: Shaped window: yes or no (default y)
-c Sends CTRL + ALT + Key (default only sends ALT + key)
-v Verbose. 0=off, 1=on (default 0)
-x # Number of buttons on the x-direction (1,2,3 or 4)
-y # Number of buttons in the y-direction (1,2,3 or 4)
-h Help. This screen.

Left mouse button:

Selects the workspace to switch to.

Right / Middle mouse buttons:

Change the number of buttons displayed.

SelfLoader is a Perl module created to load functions only on demand.

SYNOPSIS

package FOOBAR;
use SelfLoader;

... (initializing code)

__DATA__
sub {....

This module tells its users that functions in the FOOBAR package are to be autoloaded from after the __DATA__ token. See also "Autoloading" in perlsub.

The __DATA__ token

The __DATA__ token tells the perl compiler that the perl code for compilation is finished. Everything after the __DATA__ token is available for reading via the filehandle FOOBAR::DATA, where FOOBAR is the name of the current package when the __DATA__ token is reached. This works just the same as __END__ does in package main, but for other modules data after __END__ is not automatically retrievable, whereas data after __DATA__ is. The __DATA__ token is not recognized in versions of perl prior to 5.001m.

Note that it is possible to have __DATA__ tokens in the same package in multiple files, and that the last __DATA__ token in a given package that is encountered by the compiler is the one accessible by the filehandle. This also applies to __END__ and main, i.e. if the main program has an __END__, but a module required (_not_ used) by that program has a package main; declaration followed by an __DATA__, then the DATA filehandle is set to access the data after the __DATA__ in the module, _not_ the data after the __END__ token in the main program, since the compiler encounters the required file later.

SelfLoader autoloading

The SelfLoader works by the user placing the __DATA__ token after perl code which needs to be compiled and run at require time, but before subroutine declarations that can be loaded in later - usually because they may never be called.

The SelfLoader will read from the FOOBAR::DATA filehandle to load in the data after __DATA__, and load in any subroutine when it is called. The costs are the one-time parsing of the data after __DATA__, and a load delay for the _first_ call of any autoloaded function. The benefits (hopefully) are a speeded up compilation phase, with no need to load functions which are never used.
The SelfLoader will stop reading from __DATA__ if it encounters the __END__ token - just as you would expect. If the __END__ token is present, and is followed by the token DATA, then the SelfLoader leaves the FOOBAR::DATA filehandle open on the line after that token.

The SelfLoader exports the AUTOLOAD subroutine to the package using the SelfLoader, and this loads the called subroutine when it is first called.
There is no advantage to putting subroutines which will _always_ be called after the __DATA__ token.

Autoloading and package lexicals

A my $pack_lexical statement makes the variable $pack_lexical local _only_ to the file up to the __DATA__ token. Subroutines declared elsewhere _cannot_ see these types of variables, just as if you declared subroutines in the package but in another file, they cannot see these variables.

So specifically, autoloaded functions cannot see package lexicals (this applies to both the SelfLoader and the Autoloader). The vars pragma provides an alternative to defining package-level globals that will be visible to autoloaded routines. See the documentation on vars in the pragma section of perlmod.

SelfLoader and AutoLoader

The SelfLoader can replace the AutoLoader - just change use AutoLoader to use SelfLoader (though note that the SelfLoader exports the AUTOLOAD function - but if you have your own AUTOLOAD and are using the AutoLoader too, you probably know what youre doing), and the __END__ token to __DATA__. You will need perl version 5.001m or later to use this (version 5.001 with all patches up to patch m).

There is no need to inherit from the SelfLoader.

The SelfLoader works similarly to the AutoLoader, but picks up the subs from after the __DATA__ instead of in the lib/auto directory. There is a maintenance gain in not needing to run AutoSplit on the module at installation, and a runtime gain in not needing to keep opening and closing files to load subs. There is a runtime loss in needing to parse the code after the __DATA__. Details of the AutoLoader and another view of these distinctions can be found in that modules documentation.

__DATA__, __END__, and the FOOBAR::DATA filehandle.

This section is only relevant if you want to use the FOOBAR::DATA together with the SelfLoader.

Data after the __DATA__ token in a module is read using the FOOBAR::DATA filehandle. __END__ can still be used to denote the end of the __DATA__ section if followed by the token DATA - this is supported by the SelfLoader. The FOOBAR::DATA filehandle is left open if an __END__ followed by a DATA is found, with the filehandle positioned at the start of the line after the __END__ token. If no __END__ token is present, or an __END__ token with no DATA token on the same line, then the filehandle is closed.

The SelfLoader reads from wherever the current position of the FOOBAR::DATA filehandle is, until the EOF or __END__. This means that if you want to use that filehandle (and ONLY if you want to), you should either

1. Put all your subroutine declarations immediately after the __DATA__ token and put your own data after those declarations, using the __END__ token to mark the end of subroutine declarations. You must also ensure that the SelfLoader reads first by calling SelfLoader->load_stubs();, or by using a function which is selfloaded;
or
2. You should read the FOOBAR::DATA filehandle first, leaving the handle open and positioned at the first line of subroutine declarations.
You could conceivably do both.

Classes and inherited methods.

For modules which are not classes, this section is not relevant. This section is only relevant if you have methods which could be inherited.

A subroutine stub (or forward declaration) looks like

sub stub;

i.e. it is a subroutine declaration without the body of the subroutine. For modules which are not classes, there is no real need for stubs as far as autoloading is concerned.

For modules which ARE classes, and need to handle inherited methods, stubs are needed to ensure that the method inheritance mechanism works properly. You can load the stubs into the module at require time, by adding the statement SelfLoader->load_stubs(); to the module to do this.

The alternative is to put the stubs in before the __DATA__ token BEFORE releasing the module, and for this purpose the Devel::SelfStubber module is available. However this does require the extra step of ensuring that the stubs are in the module. If this is done I strongly recommend that this is done BEFORE releasing the module - it should NOT be done at install time in general.

Multiple packages and fully qualified subroutine names

Subroutines in multiple packages within the same file are supported - but you should note that this requires exporting the SelfLoader::AUTOLOAD to every package which requires it. This is done automatically by the SelfLoader when it first loads the subs into the cache, but you should really specify it in the initialization before the __DATA__ by putting a use SelfLoader statement in each package.

Fully qualified subroutine names are also supported. For example,

__DATA__
sub foo::bar {23}
package baz;
sub dob {32}

will all be loaded correctly by the SelfLoader, and the SelfLoader will ensure that the packages foo and baz correctly have the SelfLoader AUTOLOAD method when the data after __DATA__ is first parsed.