srv
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 14
pyrad 0.9
pyrad is a Python RADIUS client. more>>
pyrad is a Python RADIUS client.
pyrad contains several modules:
pyrad.client
RADIUS client class.
pyrad.dictionary
RADIUS dictionary support. Supports standard radiusd dictionaries and has preliminary support for the freeradius octets and abinary extensions.
pyrad.packet
A packet with a RADIUS request or reply. A packet object takes care of all the necessary data conversion allowing the programmer to only use standard python data types and RADIUS attribute names.
pyrad.server
Basic RADIUS server and proxy classes.
pyrad.tools
Utility functions, mostly used internally for data conversion
Simple example
Below is a simple example of how to use pyrad; it shows how to do an authentication request.
import pyrad.packet
from pyrad.client import Client
from pyrad.dictionary import Dictionary
srv=Client(server="radius.my.domain", secret="s3cr3t",
dict=Dictionary("dicts/dictionary", "dictionary.acc"))
req=srv.CreateAuthPacket(code=pyrad.packet.AccessRequest,
User_Name="wichert", NAS_Identifier="localhost")
req["User-Password"]=req.PwCrypt("password")
reply=srv.SendPacket(req)
if reply.code==pyrad.packet.AccessAccept:
print "access accepted"
else:
print "access denied"
print "Attributes returned by server:"
for i in reply.keys():
print "%s: %s" % (i, reply[i])
<<lesspyrad contains several modules:
pyrad.client
RADIUS client class.
pyrad.dictionary
RADIUS dictionary support. Supports standard radiusd dictionaries and has preliminary support for the freeradius octets and abinary extensions.
pyrad.packet
A packet with a RADIUS request or reply. A packet object takes care of all the necessary data conversion allowing the programmer to only use standard python data types and RADIUS attribute names.
pyrad.server
Basic RADIUS server and proxy classes.
pyrad.tools
Utility functions, mostly used internally for data conversion
Simple example
Below is a simple example of how to use pyrad; it shows how to do an authentication request.
import pyrad.packet
from pyrad.client import Client
from pyrad.dictionary import Dictionary
srv=Client(server="radius.my.domain", secret="s3cr3t",
dict=Dictionary("dicts/dictionary", "dictionary.acc"))
req=srv.CreateAuthPacket(code=pyrad.packet.AccessRequest,
User_Name="wichert", NAS_Identifier="localhost")
req["User-Password"]=req.PwCrypt("password")
reply=srv.SendPacket(req)
if reply.code==pyrad.packet.AccessAccept:
print "access accepted"
else:
print "access denied"
print "Attributes returned by server:"
for i in reply.keys():
print "%s: %s" % (i, reply[i])
Download (0.017MB)
Added: 2006-03-06 License: BSD License Price:
1329 downloads
AnyEvent 4.8
An identical interface to multiple event loops. more>> AnyEvent 4.8 is specifically designed to be an identical interface to multiple event loops. AnyEvent library allows module authors to utilize an event loop without forcing module users to use the same event loop (as only a single event loop can coexist peacefully at any one time).
The interface itself is vaguely similar but not identical to the Event module. On the first call of any method, the module tries to detect the currently loaded event loop by probing for an already-loaded event loop, such as Glib or Event. The first one found is used. If none is found, the module tries to load an event module.
Enhancements:
- This release adds an introductory tutorial.
- Also, many workarounds for Windows and Tk bugs have been implemented, to make AnyEvent behavior identical to Unix behavior.
- IPv6 support is only enabled when the OS actually supports it.
- BSD platforms implementing the socket structures incorrectly are now worked around. Unix domain sockets are now supported transparently.
- NAPTR and SRV handling has been improved. Lastly, a great many bugs and performance improvements have been applied, especially to AnyEvent:Handle and TLS support.
Requirements: Perl
Added: 2009-07-07 License: Perl Artistic License Price: FREE
14 downloads
nss_ldap 248
nss_ldap is an RFC 2307-compliant set of C library extensions. more>>
nss_ldap is an RFC 2307-compliant set of C library extensions.
The resolution of the entities defined in RFC 2307 is generally performed by a set of UNIX C library calls (such as getpwnam() to return the attributes of a user).
The nss_ldap module provides the means for Solaris and Linux workstations to this information (such as users, hosts, and groups) from LDAP directories.
The module is the reference implementation of RFC 2307, and has been studied by vendors such as Sun (who developed the original Name Service Switch interface).
Main features:
- Support for the RFC 2307/RFC 2307bis (including netgroups) as well as user-defined schema
- Common implementation across platforms
- Support for Kerberos and SSL authentication, integrity and privacy
- Configuration file compatibility with pam_ldap
- Bootstraps from the DNS using SRV records
- Support for AIX, glibc, IRS and ONC+ name service switches
- Support for RFC 2307bis groups (including nested groups)
- Specific Active Directory support including incremental retrieval of multi-valued attributes
- Directory-based authentication for platforms that lack PAM (AIX 4.3.3)
<<lessThe resolution of the entities defined in RFC 2307 is generally performed by a set of UNIX C library calls (such as getpwnam() to return the attributes of a user).
The nss_ldap module provides the means for Solaris and Linux workstations to this information (such as users, hosts, and groups) from LDAP directories.
The module is the reference implementation of RFC 2307, and has been studied by vendors such as Sun (who developed the original Name Service Switch interface).
Main features:
- Support for the RFC 2307/RFC 2307bis (including netgroups) as well as user-defined schema
- Common implementation across platforms
- Support for Kerberos and SSL authentication, integrity and privacy
- Configuration file compatibility with pam_ldap
- Bootstraps from the DNS using SRV records
- Support for AIX, glibc, IRS and ONC+ name service switches
- Support for RFC 2307bis groups (including nested groups)
- Specific Active Directory support including incremental retrieval of multi-valued attributes
- Directory-based authentication for platforms that lack PAM (AIX 4.3.3)
Download (0.23MB)
Added: 2006-02-15 License: LGPL (GNU Lesser General Public License) Price:
1349 downloads
sipsak 0.9.6
sipsak is a command line tool for performing various tests on Session Initiation Protocol (SIP) applications and devices. more>>
sipsak is a small comand line tool for developers and administrators of Session Initiation Protocol (SIP) applications. sipsak can be used for some simple tests on SIP applications and devices.
Main features:
- sending OPTIONS request
- sending text files (which should contain SIP requests)
- traceroute (see section 11 in RFC3261)
- user location test
- flooding test
- random character trashed test
- interpret and react on response
- authentication with qop supported
- short notation supported for receiving (not for sending)
- string replacement in files
- can simulate calls in usrloc mode
- uses symmetric signaling and thus should work behind NAT
- can upload any given contact to a registrar
- send messages to any SIP destination
- Nagios compliant return codes
- search for strings in reply with regluar expression
- use multiple processes to create more server load
- read SIP message from STDIN (e.g. from a pipe |)
- supports DNS SRV through libruli
Version restrictions:
- The hostname is used in the Via line, which is not correct in all cases (e.g. if the loopback interface is used, or if the host has several interfaces). The rport parameter should fix problmes with the incorrect hostname, but for backward compatibility whith implementations which do not support rport this should be fixed.
- The DNS responses are not parsed compeltly which can result in strange output during hostname detection.
- TCP is not supported as transport protocol.
- IPv6 is not supported as transport protocol.
- Missing support for the Record-Route and Route header.
- Not fully RFC3261 compatible.
- Some smaller problems are listed in the TODO file.
Enhancements:
- A new option allows to add any header to the outgoing requests.
- The variable replacement option now accepts any number of attribute value pairs.
- Besides MD5 now SHA1 is support as digest authentication algorithm.
- The password for authentication can be read from stdin to prevent password disclosure in the process list.
- Fixed problems when executed as user root and compiles fine again under cygwin.
<<lessMain features:
- sending OPTIONS request
- sending text files (which should contain SIP requests)
- traceroute (see section 11 in RFC3261)
- user location test
- flooding test
- random character trashed test
- interpret and react on response
- authentication with qop supported
- short notation supported for receiving (not for sending)
- string replacement in files
- can simulate calls in usrloc mode
- uses symmetric signaling and thus should work behind NAT
- can upload any given contact to a registrar
- send messages to any SIP destination
- Nagios compliant return codes
- search for strings in reply with regluar expression
- use multiple processes to create more server load
- read SIP message from STDIN (e.g. from a pipe |)
- supports DNS SRV through libruli
Version restrictions:
- The hostname is used in the Via line, which is not correct in all cases (e.g. if the loopback interface is used, or if the host has several interfaces). The rport parameter should fix problmes with the incorrect hostname, but for backward compatibility whith implementations which do not support rport this should be fixed.
- The DNS responses are not parsed compeltly which can result in strange output during hostname detection.
- TCP is not supported as transport protocol.
- IPv6 is not supported as transport protocol.
- Missing support for the Record-Route and Route header.
- Not fully RFC3261 compatible.
- Some smaller problems are listed in the TODO file.
Enhancements:
- A new option allows to add any header to the outgoing requests.
- The variable replacement option now accepts any number of attribute value pairs.
- Besides MD5 now SHA1 is support as digest authentication algorithm.
- The password for authentication can be read from stdin to prevent password disclosure in the process list.
- Fixed problems when executed as user root and compiles fine again under cygwin.
Download (0.14MB)
Added: 2006-01-29 License: GPL (GNU General Public License) Price:
1367 downloads
libevnet 0.3.8
libevnet provides a suite of interfaces useful in network applications. more>>
libevnet library provides a suite of interfaces, all built around libevent [http://www.monkey.org/~provos/libevent] , useful to network daemons.
bufio.h: Non-blocking line and block buffered I/O routines, providing tail recursive behavior so callers cannot overflow their stack with multiple back-to-back I/O issues (i.e. attempting unbounded recursive I/O operations before falling into the event loop).
This feature preserves the natural way to code in an asychronous manner by safeguarding against certain types of pathological behavior and malicious attacks.
socket.h: Asychronous accept(2) and connect(2), supporting IPv4, IPv6 and Unix Domain sockets transparently. Also supports encapsulated host address lookups for "one-shot" connection handling with automatic fallback (for MX and SRV hosts).
tls.h: OpenSSL interface which plugs into the buffered I/O API in bufio.h and socket.h API.
thread.h: Threading implementation for running "blocking" routines asychronously. Run a function in a separate thread, and have the return value collected and passed back asynchronously to the original caller.
lookup.h: Comprehensive DNS resolver with a dead simple interface. Supports PTR, A, AAAA, CNAME, NS, MX, TXT, SOA and SRV records, as well as "compound queries".
A lookup of A+AAAA+SRV first queries the SRV records, sorts them, then resolves each SRV host to an A and/or AAAA host (with a configurable CNAME chaining limit). The response is a linked list of lookup structures, beginning with an SRV record, associated A/AAAA sockaddr structures, the next SRV record, and so on. A+MX has similar behavior. This feature actually reduces network traffic, since most of the time the initial DNS query response contains all the necessary information in the additional section.
DNS SRV records are compliantly sorted according to RFC 2782 [http://rfc-ref.org/RFC-TEXTS/2782/]
Enhancements:
- The platform compatibility library was refactored.
<<lessbufio.h: Non-blocking line and block buffered I/O routines, providing tail recursive behavior so callers cannot overflow their stack with multiple back-to-back I/O issues (i.e. attempting unbounded recursive I/O operations before falling into the event loop).
This feature preserves the natural way to code in an asychronous manner by safeguarding against certain types of pathological behavior and malicious attacks.
socket.h: Asychronous accept(2) and connect(2), supporting IPv4, IPv6 and Unix Domain sockets transparently. Also supports encapsulated host address lookups for "one-shot" connection handling with automatic fallback (for MX and SRV hosts).
tls.h: OpenSSL interface which plugs into the buffered I/O API in bufio.h and socket.h API.
thread.h: Threading implementation for running "blocking" routines asychronously. Run a function in a separate thread, and have the return value collected and passed back asynchronously to the original caller.
lookup.h: Comprehensive DNS resolver with a dead simple interface. Supports PTR, A, AAAA, CNAME, NS, MX, TXT, SOA and SRV records, as well as "compound queries".
A lookup of A+AAAA+SRV first queries the SRV records, sorts them, then resolves each SRV host to an A and/or AAAA host (with a configurable CNAME chaining limit). The response is a linked list of lookup structures, beginning with an SRV record, associated A/AAAA sockaddr structures, the next SRV record, and so on. A+MX has similar behavior. This feature actually reduces network traffic, since most of the time the initial DNS query response contains all the necessary information in the additional section.
DNS SRV records are compliantly sorted according to RFC 2782 [http://rfc-ref.org/RFC-TEXTS/2782/]
Enhancements:
- The platform compatibility library was refactored.
Download (0.053MB)
Added: 2007-05-07 License: MIT/X Consortium License Price:
900 downloads
gvfsfind 0.1.4
gvfsfind searches for files in a directory hierarchy. more>>
gvfsfind searches for files in a directory hierarchy. This project is inspired by the Unix find utility, but operates on URLs using gnome-vfs instead of the local file system.
For example, gvfsfind.py ftp://video.foo.org --type d --print prints all directories on the FTP server. gvfsfind.py ssh://skipper/srv/movie --type f -name ".*.vob" --exec "gnomevfs-copy %u ." copies all files ending with .vob from the host skippers directory /srv/movie, including its sub-directories.
Enhancements:
- A makefile has been added to simplify release.
- This release is packaged as a tar.gz archive.
- Support has been added for filenames including #.
- Support for use as a Python module has been added.
<<lessFor example, gvfsfind.py ftp://video.foo.org --type d --print prints all directories on the FTP server. gvfsfind.py ssh://skipper/srv/movie --type f -name ".*.vob" --exec "gnomevfs-copy %u ." copies all files ending with .vob from the host skippers directory /srv/movie, including its sub-directories.
Enhancements:
- A makefile has been added to simplify release.
- This release is packaged as a tar.gz archive.
- Support has been added for filenames including #.
- Support for use as a Python module has been added.
Download (0.008MB)
Added: 2007-08-13 License: GPL (GNU General Public License) Price:
803 downloads
Resolver User Layer Interface 0.36
RULI stands for Resolver User Layer Interface. more>>
RULI stands for Resolver User Layer Interface. Its a library built on top of an asynchronous DNS stub resolver. RULI provides an easy-to-use interface for querying DNS SRV resource records. The goal is to promote wide deployment of SRV-cognizant software. RULI aims to fully support SRV-related standards. There are bindings for PHP, Perl, Guile/Scheme, Java, and Lua. IPv6 is supported.
Now you can understand the benefits of SRV records and please see how RULI can help you.
SRV records are more complex than A records
Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you
The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic
Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.
RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech
<<lessNow you can understand the benefits of SRV records and please see how RULI can help you.
SRV records are more complex than A records
Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you
The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic
Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.
RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech
Download (0.12MB)
Added: 2006-07-15 License: GPL (GNU General Public License) Price:
1197 downloads
MyDNSConfig 1.1.0
MyDNSConfig is a web-based control panel for the MYDNS name server. more>>
MyDNSConfig project is a web-based control panel for the MYDNS name server.
MyDNSConfig is licensed under BSD license.
MyDNS is designed to serve DNS records directly from a MySQL database.
MyDNSConfig is a web-interface to the MyDNS database.
Main features:
- A records
- AAAA records
- ALIAS records
- CNAME records
- HINFO records
- MX records
- NS records
- PTR records (for reverse lookups)
- RP records
- SRV records
- TXT records (and therefore also SPF records)
Enhancements:
- This release fixes several bugs in the user management system and adds a new interface theme.
<<lessMyDNSConfig is licensed under BSD license.
MyDNS is designed to serve DNS records directly from a MySQL database.
MyDNSConfig is a web-interface to the MyDNS database.
Main features:
- A records
- AAAA records
- ALIAS records
- CNAME records
- HINFO records
- MX records
- NS records
- PTR records (for reverse lookups)
- RP records
- SRV records
- TXT records (and therefore also SPF records)
Enhancements:
- This release fixes several bugs in the user management system and adds a new interface theme.
Download (0.095MB)
Added: 2007-03-06 License: BSD License Price:
969 downloads
Class::DBI::Plugin::FilterOnClick 1.0
Class::DBI::Plugin::FilterOnClick is a Perl module to generate browsable and searchable HTML Tables. more>>
Class::DBI::Plugin::FilterOnClick is a Perl module to generate browsable and searchable HTML Tables using FilterOnClick in conjunction with Class::DBI.
SYNOPSIS
# Inside of your sub-class of Class::DBI add these lines:
use Class::DBI::Plugin::FilterOnClick;
use Class::DBI::Pager;
use Class::DBI::AbstractSearch;
use Class::DBI::Plugin::AbstractCount;
use Class::DBI::Plugin::RetrieveAll;
.....
# Inside your script you will be able to use this modules
# methods on your table class or object as needed.
use ClassDBIBaseClass;
use URI::Escape;
use CGI;
my $cgi = CGI->new();
my %params;
map { $params{$_} =
uri_unescape($cgi->param("$_"))
} $cgi->param();
my $filteronclick = Baseball::Master->filteronclick(
-config_file => /srv/www/cgi-bin/baseball.ini,
# -rows => $cgi->param(rows) || 15 ,
-on_page => $cgi->param(page) || 1,
-params => %params );
$filteronclick->field_to_column(
lastname => Last Name . $html->order_by_link(lastname),
firstname => First Name . $html->order_by_link(firstname),
bats => Bats,
throws => Throws,
ht_ft => Height Ft,
ht_in => In,
wt => Weight,
birthyear => Birthyear,
birthstate => Birthstate,
_FilterOnClickCustom1_ => Other Data,
_FilterOnClickCustom2_ => More Data
);
FilterOnClickCustom
$filteronclick->data_table->addRow(
Last Name,
First Name,
Bats ,
Throws ,
Height (ft),
(inches),
Weight,
Birth Year );
$filteronclick->params( $cgi->Vars; );
$filteronclick->exclude_from_url([ page ]);
# indicate which columns to exclude, inverse of display above
# can be set in config file as well
$filteronclick->exclude_columns();
# indicate the base class to work with, this is optional,
# if you should create you object via a call to
# Class::DBI::Plugin::FilterOnClick vs. a Class::DBI sub class
# this assures the correct sub class is used for data collection
$filteronclick->cdbi_class( Baseball::Master );
# indicate the style of navigation to provide
$filteronclick->navigation_style( both );
print qq~ Filter by First Letter of Last Name ~;
print $filteronclick->string_filter_navigation(
-column => lastname,
-position => begins,
);
print qq~ ~;
$filteronclick->only(firstname);
print $filteronclick->build_table(
_FilterOnClickCustom1_ => sub {
my $pid = shift; # pid = Primary ID of the record in the base table
my @status_objects = Baseball::Allstars->search(lahmanid => $pid);
if (@status_objects) {
my $years;
foreach my $st (@status_objects) {
$years .= $st->year() . " ";
}
return $years;
}
return NA;
},
_FilterOnClickCustom2_ => sub {
my $pid = shift; # pid = Primary ID of the record in the base table
my @status_objects = Baseball::Allstars->search(lahmanid => $pid);
if (@status_objects) {
my $teams;
foreach my $st (@status_objects) {
$teams .= $st->team() . " ";
}
return $teams;
}
return NA;
},
);
my $nav = $filteronclick->html_table_navigation();
print qq!
$filteronclick->add_bottom_span($nav);
print $filteronclick->data_table;
UPGRADE WARNING
As of the .8 release there have been changes to the methods and how they work. It is likely that scripts built with older versions WILL break. Please read below to find specific changes that may negatively impact scripts built using the the releases prior to .8. The 1.0 release contains some minor modifications that could in some chases break your scripts, test carefully before upgrading in a production environment.
The intention of this module is to simplify the creation of browsable and searchable HTML tables without having to write the HTML, either in your script or in templates.
It is intended for use inside of other frameworks such as Embperl, Apache::ASP or even CGI. It does not aspire to be its own framework. If you are looking for a frameworks which allow using Class::DBI I suggest you look into the Maypole or the Catalyst module.
See FilterOnClick below for more on the purpose of this module.
Tables are created using HTML::Table. The use of HTML::Table was selected because it allows for several advanced sorting techniques that can provide for easy manipulation of the data outside of the SQL statement. This is very useful in scenarios where you want to provide/test a sort routine and not write SQL for it. The more I use this utility the less likely it seems that one would need to leverage this, but it is an option if you want to explore it.
Feedback on this module, its interface, usage, documentation etc. is welcome.
<<lessSYNOPSIS
# Inside of your sub-class of Class::DBI add these lines:
use Class::DBI::Plugin::FilterOnClick;
use Class::DBI::Pager;
use Class::DBI::AbstractSearch;
use Class::DBI::Plugin::AbstractCount;
use Class::DBI::Plugin::RetrieveAll;
.....
# Inside your script you will be able to use this modules
# methods on your table class or object as needed.
use ClassDBIBaseClass;
use URI::Escape;
use CGI;
my $cgi = CGI->new();
my %params;
map { $params{$_} =
uri_unescape($cgi->param("$_"))
} $cgi->param();
my $filteronclick = Baseball::Master->filteronclick(
-config_file => /srv/www/cgi-bin/baseball.ini,
# -rows => $cgi->param(rows) || 15 ,
-on_page => $cgi->param(page) || 1,
-params => %params );
$filteronclick->field_to_column(
lastname => Last Name . $html->order_by_link(lastname),
firstname => First Name . $html->order_by_link(firstname),
bats => Bats,
throws => Throws,
ht_ft => Height Ft,
ht_in => In,
wt => Weight,
birthyear => Birthyear,
birthstate => Birthstate,
_FilterOnClickCustom1_ => Other Data,
_FilterOnClickCustom2_ => More Data
);
FilterOnClickCustom
$filteronclick->data_table->addRow(
Last Name,
First Name,
Bats ,
Throws ,
Height (ft),
(inches),
Weight,
Birth Year );
$filteronclick->params( $cgi->Vars; );
$filteronclick->exclude_from_url([ page ]);
# indicate which columns to exclude, inverse of display above
# can be set in config file as well
$filteronclick->exclude_columns();
# indicate the base class to work with, this is optional,
# if you should create you object via a call to
# Class::DBI::Plugin::FilterOnClick vs. a Class::DBI sub class
# this assures the correct sub class is used for data collection
$filteronclick->cdbi_class( Baseball::Master );
# indicate the style of navigation to provide
$filteronclick->navigation_style( both );
print qq~ Filter by First Letter of Last Name ~;
print $filteronclick->string_filter_navigation(
-column => lastname,
-position => begins,
);
print qq~ ~;
$filteronclick->only(firstname);
print $filteronclick->build_table(
_FilterOnClickCustom1_ => sub {
my $pid = shift; # pid = Primary ID of the record in the base table
my @status_objects = Baseball::Allstars->search(lahmanid => $pid);
if (@status_objects) {
my $years;
foreach my $st (@status_objects) {
$years .= $st->year() . " ";
}
return $years;
}
return NA;
},
_FilterOnClickCustom2_ => sub {
my $pid = shift; # pid = Primary ID of the record in the base table
my @status_objects = Baseball::Allstars->search(lahmanid => $pid);
if (@status_objects) {
my $teams;
foreach my $st (@status_objects) {
$teams .= $st->team() . " ";
}
return $teams;
}
return NA;
},
);
my $nav = $filteronclick->html_table_navigation();
print qq!
$nav
n!; $filteronclick->add_bottom_span($nav);
print $filteronclick->data_table;
UPGRADE WARNING
As of the .8 release there have been changes to the methods and how they work. It is likely that scripts built with older versions WILL break. Please read below to find specific changes that may negatively impact scripts built using the the releases prior to .8. The 1.0 release contains some minor modifications that could in some chases break your scripts, test carefully before upgrading in a production environment.
The intention of this module is to simplify the creation of browsable and searchable HTML tables without having to write the HTML, either in your script or in templates.
It is intended for use inside of other frameworks such as Embperl, Apache::ASP or even CGI. It does not aspire to be its own framework. If you are looking for a frameworks which allow using Class::DBI I suggest you look into the Maypole or the Catalyst module.
See FilterOnClick below for more on the purpose of this module.
Tables are created using HTML::Table. The use of HTML::Table was selected because it allows for several advanced sorting techniques that can provide for easy manipulation of the data outside of the SQL statement. This is very useful in scenarios where you want to provide/test a sort routine and not write SQL for it. The more I use this utility the less likely it seems that one would need to leverage this, but it is an option if you want to explore it.
Feedback on this module, its interface, usage, documentation etc. is welcome.
Download (0.024MB)
Added: 2006-11-29 License: Perl Artistic License Price:
1060 downloads
Php AjaX with Smarty Templates 1.0.0 RC1
Php AjaX with Smarty Templates (PAXT) is a library built on top of the HTML_AJAX package and using Smarty templates. more>>
Php AjaX with Smarty Templates (PAXT) is a library built on top of the HTML_AJAX package and using Smarty templates.
Download paxt and put it somewhere you can include it (eg. add it to your include path, or you will include it via its path)
classes.php
include paxt widget class
< ?
require_once "paxt/lib/widget.class.php";
require_once "paxt/lib/server.class.php";
? >
define main class
derived from widget? class
< ?
class myindex extends widget {
function __construct() {
$this->template="myindex.html";
$this->exportMethod("launch");//export $this->launch to be used from javascript
parent::__construct(true);//main widget always is fully instantiated
}
function launch() {
return $this->launchWindow(new launched(true));
}
}
? >
define second class
, which will be launched by myindex
< ?
class launched extends widget {
function __construct($parent=null) {
$this->template="launched.html";
parent::__construct($parent);
if ($parent) {
$this->data->variable = $this->modal_parent->data->variable;
}
}
}
? >
index.php5
create file index.php5, which will be gate to your application
include your classes
< ?
require_once "classes.php";
? >
start session
object will be stored in sessions
< ?
session_start();
?>
create server object
and give name of first page ...
$srv = new server(myindex);
? >
... and register class prototype of second class ....
< ?
$srv->register_prot(myindex);
? >
... and give command to run everything :)
$srv->run();
?>
server.php5
Create server.php5 which will be launched by javascript to handle requests
< ?
require_once "classes.php";
require_once "HTML/AJAX/Server.php";
//start session
session_start();
$pages=&$_SESSION["registered_pages"];
$s = new HTML_AJAX_Server();
$s->registerJsLibrary("paxt","server.js",dirname(__FILE__)."/paxt/lib/");
foreach($pages AS $page) {
$s->registerClass($page,$page->getClass());
}
$s->handleRequest();
? >
As you see, you need to write lot of stuff by hand, but I hope that it will be included later in server? class.
Enhancements:
- A more stable and clean API.
- Input fields validation.
- Many bugfixes.
<<lessDownload paxt and put it somewhere you can include it (eg. add it to your include path, or you will include it via its path)
classes.php
include paxt widget class
< ?
require_once "paxt/lib/widget.class.php";
require_once "paxt/lib/server.class.php";
? >
define main class
derived from widget? class
< ?
class myindex extends widget {
function __construct() {
$this->template="myindex.html";
$this->exportMethod("launch");//export $this->launch to be used from javascript
parent::__construct(true);//main widget always is fully instantiated
}
function launch() {
return $this->launchWindow(new launched(true));
}
}
? >
define second class
, which will be launched by myindex
< ?
class launched extends widget {
function __construct($parent=null) {
$this->template="launched.html";
parent::__construct($parent);
if ($parent) {
$this->data->variable = $this->modal_parent->data->variable;
}
}
}
? >
index.php5
create file index.php5, which will be gate to your application
include your classes
< ?
require_once "classes.php";
? >
start session
object will be stored in sessions
< ?
session_start();
?>
create server object
and give name of first page ...
$srv = new server(myindex);
? >
... and register class prototype of second class ....
< ?
$srv->register_prot(myindex);
? >
... and give command to run everything :)
$srv->run();
?>
server.php5
Create server.php5 which will be launched by javascript to handle requests
< ?
require_once "classes.php";
require_once "HTML/AJAX/Server.php";
//start session
session_start();
$pages=&$_SESSION["registered_pages"];
$s = new HTML_AJAX_Server();
$s->registerJsLibrary("paxt","server.js",dirname(__FILE__)."/paxt/lib/");
foreach($pages AS $page) {
$s->registerClass($page,$page->getClass());
}
$s->handleRequest();
? >
As you see, you need to write lot of stuff by hand, but I hope that it will be included later in server? class.
Enhancements:
- A more stable and clean API.
- Input fields validation.
- Many bugfixes.
Download (0.12MB)
Added: 2007-05-07 License: GPL (GNU General Public License) Price:
904 downloads
Berkeley Unified Parallel C 2.4.0
Berkeley Unified Parallel C (UPC) is an extension of the C programming language. more>>
Unified Parallel C, in short UPC, is an extension of the C programming language designed for high performance computing on large-scale parallel machines.
The language provides a uniform programming model for both shared and distributed memory hardware.
The programmer is presented with a single shared, partitioned address space, where variables may be directly read and written by any processor, but each variable is physically associated with a single processor.
UPC uses a Single Program Multiple Data (SPMD) model of computation in which the amount of parallelism is fixed at program startup time, typically with a single thread of execution per processor.
Whats New in This Release:
- Add initial native support for the Cray XT3 via new portals network
- Implement the GASP 1.5 performance instrumentation interface, supporting the
Parallel Performance Wizard (PPW) and other third-party profiling tools.
- Add bupc_ticks_to_ns() - finer granularity timer query
- Add the Berkeley implementations of the UPC collectives and UPC-IO to GCCUPC+UPCR
- Add most of the Berkeley UPC library extensions to GCCUPC+UPCR
- Add upcdecl command-line tool (also online at: http://upc.lbl.gov/upcdecl)
- Add support for alloca() and stdarg.h
- Performance improvements to the BUPC semaphore library for signalling store
- Add bupc_thread_distance() - runtime thread layout query for hierarchical systems
- Add a remote fetch-and-add UPC library extension (initially just for 64-bit ints)
- Allow configure-time tuning of bit distribution in packed pointer-to-shared rep
- Fix the following notable bugs in 2.2.2 (see http://upc-bugs.lbl.gov for details):
- bug525: optimizer crashes on Tru64/CompaqC for libgasnet
- bug1229: More robust preprocessing on Compaq C
- bug1389: ansi-aliasing violations on small local put/get copies
- bug1531: improved lock fairness to remote lock requests
- bug1594: timer inaccuracies on Cray X1E
- bug1645: preprocess-time failure Backslash found where operator expected
- bug1657: PACKAGE_* symbols exposed to UPC code on GCCUPC+UPCR
- bug1683: improve upcrun handling of -shared-heap-max
- bug 1743: More robust behavior when backend C compiler changes
- Improved SRV-based DNS failover for upcc HTTP translation
- Add gzip compression to HTTP netcompile, for faster compiles over slow links
- Improved robustness for SSH netcompile to handle stray output from dotfiles
- Numerous misc minor bug fixes
<<lessThe language provides a uniform programming model for both shared and distributed memory hardware.
The programmer is presented with a single shared, partitioned address space, where variables may be directly read and written by any processor, but each variable is physically associated with a single processor.
UPC uses a Single Program Multiple Data (SPMD) model of computation in which the amount of parallelism is fixed at program startup time, typically with a single thread of execution per processor.
Whats New in This Release:
- Add initial native support for the Cray XT3 via new portals network
- Implement the GASP 1.5 performance instrumentation interface, supporting the
Parallel Performance Wizard (PPW) and other third-party profiling tools.
- Add bupc_ticks_to_ns() - finer granularity timer query
- Add the Berkeley implementations of the UPC collectives and UPC-IO to GCCUPC+UPCR
- Add most of the Berkeley UPC library extensions to GCCUPC+UPCR
- Add upcdecl command-line tool (also online at: http://upc.lbl.gov/upcdecl)
- Add support for alloca() and stdarg.h
- Performance improvements to the BUPC semaphore library for signalling store
- Add bupc_thread_distance() - runtime thread layout query for hierarchical systems
- Add a remote fetch-and-add UPC library extension (initially just for 64-bit ints)
- Allow configure-time tuning of bit distribution in packed pointer-to-shared rep
- Fix the following notable bugs in 2.2.2 (see http://upc-bugs.lbl.gov for details):
- bug525: optimizer crashes on Tru64/CompaqC for libgasnet
- bug1229: More robust preprocessing on Compaq C
- bug1389: ansi-aliasing violations on small local put/get copies
- bug1531: improved lock fairness to remote lock requests
- bug1594: timer inaccuracies on Cray X1E
- bug1645: preprocess-time failure Backslash found where operator expected
- bug1657: PACKAGE_* symbols exposed to UPC code on GCCUPC+UPCR
- bug1683: improve upcrun handling of -shared-heap-max
- bug 1743: More robust behavior when backend C compiler changes
- Improved SRV-based DNS failover for upcc HTTP translation
- Add gzip compression to HTTP netcompile, for faster compiles over slow links
- Improved robustness for SSH netcompile to handle stray output from dotfiles
- Numerous misc minor bug fixes
Download (MB)
Added: 2006-11-18 License: BSD License Price:
1072 downloads
tcptunnel 1.0
tcptunnel is a simple TCP tunnel written in Perl. more>>
tcptunnel is a simple TCP tunnel written in Perl.
Also is a versatile tcp tunnel. The tcptunnel uses:
- tunnelling through a firewall or proxy
- redirecting tcp connections to other ports or machines
- debugging tcp connections in-place
- packet sniffing
The tcptunnel listens on local port < port > and when a connection is made it connects the other end of the tunnel as follows:
a) With no proxy specified, it connects the other end
to < srvport > on < srv >.
b) With a proxy, it connects to < srvport > on < proxy >.
It then directs the proxy to telnet to < srv >, and then it connects the ends of the tunnel.
<<lessAlso is a versatile tcp tunnel. The tcptunnel uses:
- tunnelling through a firewall or proxy
- redirecting tcp connections to other ports or machines
- debugging tcp connections in-place
- packet sniffing
The tcptunnel listens on local port < port > and when a connection is made it connects the other end of the tunnel as follows:
a) With no proxy specified, it connects the other end
to < srvport > on < srv >.
b) With a proxy, it connects to < srvport > on < proxy >.
It then directs the proxy to telnet to < srv >, and then it connects the ends of the tunnel.
Download (0.005MB)
Added: 2006-07-01 License: GPL (GNU General Public License) Price:
1213 downloads
Zoned 0.1.1
Zoned project provides DNS zone database clustering for BIND9. more>>
Zoned project provides DNS zone database clustering for BIND9.
Zoned works in conjunction with the BDBHPT DLZ module for BIND9 (9.4.0+). Zoned manages the backing-store Berkeley DB database, and utilizes the Berkeley DB Replication Base API to provide high availability and load distribution to a coherent DNS zone infrastructure.
Zoned includes the zoned(1) server replication node, zonectl(1) command line utility for managing server nodes and editing DNS zone records, and a Perl module, Zoned. All changes to DNS zone data must be processed through a Zoned node, preferably using the command-line utility or Perl library. Alternatively, an ASN.1 message schema definition is provided, defining the messaging protocol for node communication, which can be used to build your own tools for interacting with the cluster.
Zoned and Berkeley DB autonomously manage the cluster and cluster messaging (including transparently routing all zoned edits to the master, per BerkeleyDB Replication requirements). You must enumerate cluster nodes through SRV resource records. This list specifies all nodes which should participate in the cluster, not necessarily all available nodes. This list determines who and where each node should peer with, and serves as a parameter to determining whether a transaction has been successfully committed (more than one-half of enumerated nodes have written out a zone edit). The SRV node enumeration modifications are automatically detected with a configurable check interval.
To compile Zoned you need: GNU Make, libarena, libevnet, libevent, asn1c, and Lua.
Zoned has been successfully compiled and run on Debian GNU/Linux i386, and OpenBSD 4.0 AMD64 platforms. Zoned is new software, and it may take some elbow grease to build properly.
libevnet requires C-Ares and OpenSSL.
Zoned is a Work-in-Progress. Node authentication is not yet implemented, but will use TLS and X.509 certificate verification. Currently node discovery occurs through an SRV query, which is expected to enumerate all current nodes.
<<lessZoned works in conjunction with the BDBHPT DLZ module for BIND9 (9.4.0+). Zoned manages the backing-store Berkeley DB database, and utilizes the Berkeley DB Replication Base API to provide high availability and load distribution to a coherent DNS zone infrastructure.
Zoned includes the zoned(1) server replication node, zonectl(1) command line utility for managing server nodes and editing DNS zone records, and a Perl module, Zoned. All changes to DNS zone data must be processed through a Zoned node, preferably using the command-line utility or Perl library. Alternatively, an ASN.1 message schema definition is provided, defining the messaging protocol for node communication, which can be used to build your own tools for interacting with the cluster.
Zoned and Berkeley DB autonomously manage the cluster and cluster messaging (including transparently routing all zoned edits to the master, per BerkeleyDB Replication requirements). You must enumerate cluster nodes through SRV resource records. This list specifies all nodes which should participate in the cluster, not necessarily all available nodes. This list determines who and where each node should peer with, and serves as a parameter to determining whether a transaction has been successfully committed (more than one-half of enumerated nodes have written out a zone edit). The SRV node enumeration modifications are automatically detected with a configurable check interval.
To compile Zoned you need: GNU Make, libarena, libevnet, libevent, asn1c, and Lua.
Zoned has been successfully compiled and run on Debian GNU/Linux i386, and OpenBSD 4.0 AMD64 platforms. Zoned is new software, and it may take some elbow grease to build properly.
libevnet requires C-Ares and OpenSSL.
Zoned is a Work-in-Progress. Node authentication is not yet implemented, but will use TLS and X.509 certificate verification. Currently node discovery occurs through an SRV query, which is expected to enumerate all current nodes.
Download (0.087MB)
Added: 2007-05-11 License: GPL (GNU General Public License) Price:
896 downloads
LFTP 3.5.12
LFTP is sophisticated file transfer program with command line interface. more>>
LFTP is sophisticated file transfer program with command line interface. LFTP supports FTP, HTTP, FISH, SFTP, HTTPS and FTPS protocols. GNU Readline library is used for input.
Every operation in lftp is reliable, that is any non-fatal error is handled and the operation is retried automatically. So if downloading breaks, it will be restarted from the point automatically. Even if ftp server does not support REST command, lftp will try to retrieve the file from the very beginning until the file is transferred completely. This is useful for dynamic-ip machines which change their IP addresses quite often, and for sites with very bad internet connectivity.
If you exit lftp when some jobs are not finished yet, lftp will move itself to nohup mode in background. The same happens when you have a real modem hangup or when you close an xterm.
lftp has shell-like command syntax allowing you to launch several commands in parallel in background (&). It is also possible to group commands within () and execute them in background. All background jobs are executed in the same single process. You can bring a foreground job to background with ^Z (c-z) and back with command `wait (or `fg which is alias to `wait). To list running jobs, use command `jobs. Some commands allow redirecting their output (cat, ls, ...) to file or via pipe to external command. Commands can be executed conditionally based on termination status of previous command (&&, ||).
Examples:
lftp> cat file | gzip > file.gz
lftp> get file &
lftp> (cd /path && get file) &
The first command retrieves file from ftp server and passes its contents to gzip which in turn stores compressed data to file.gz. Other commands show how to start commands or command groups in background.
lftp has builtin mirror which can download or update a whole directory tree. There is also reverse mirror (mirror -R) which uploads or updates a directory tree on server.
There is command `at to launch a job at specified time in current context, command `queue to queue commands for sequential execution for current server, and much more.
LFTP supports IPv6 for both FTP and HTTP protocols. For FTP protocol it uses method described in RFC2428.
Other low level stuff supported: ftp proxy, http proxy, ftp over http, opie/skey, fxp transfers, socks.
If lftp was compiled with ssl support, then it includes software developed by the OpenSSL.
Main features:
- FTP and HTTP protocols support.
- FTP (e.g. TIS FWTK) proxy support.
- HTTP proxy support.
- FTP over HTTP proxy support (hftp).
- HTTPS and FTPS protocols support using OpenSSL library.
- Automatic OPIE/SKEY support in FTP protocol.
- FXP transfers support (between two FTP servers, bypassing client machine).
- FTP listings support: unix-style, NT, EPLF.
- Automatic reconnect and retry of an operation on retriable errors or timeout.
- IPv6 support in both FTP and HTTP.
- FISH protocol support. It uses ssh with no special program on server side.
- SFTP protocol v3 and v4 support.
- HTTP/1.1 keep-alive support.
- Experimental support for SRV DNS records.
- SOCKS support (configure option).
- Modification time preservation (if server can report it).
- `reget and `reput support.
- Built-in mirror and reverse mirror (mirror -R).
- Transfer rate throttling for each connection and for all connections in sum.
- Limit for number of connections to the same site. Interruption of background transfer to do a foreground operation when the limit is reached.
- Socket options tuning: buffer size and maximum segment size.
- Job queueing.
- Job execution at specified time.
- Comprehensive scripting support.
- URL recognition in most operations.
- Readline library is used for input.
- Context sensitive completion.
- Bash-like prompt extensions.
- Launching of local shell commands.
- Suspend support.
- Bookmarks.
- Aliases.
- Saving of last directory on each site. `cd - to go there.
- Copying of files between two servers, e.g. between FTP and HTTP.
- Numerous settings which can be associated with a specific server or a group.
- Paging of remote files using external program.
- `zcat and `zmore support.
- Help for commands.
- Command history saved in a file.
- Transfer status includes rate and ETA.
- File listing cache.
- Background jobs (bash-like).
- Job output redirection to a file or to a program via pipe.
- Conditional commands depending on exit status of previous one.
- Loading of binary modules at run time (configure option).
- `pget to download a file using several connections.
- `mirror can download several files in parallel (--parallel option).
- Slots. Each slot is a separate session, switch using Meta-{1-9} or `slot command. Refer to a slot site using pseudo URL slot:name.
<<lessEvery operation in lftp is reliable, that is any non-fatal error is handled and the operation is retried automatically. So if downloading breaks, it will be restarted from the point automatically. Even if ftp server does not support REST command, lftp will try to retrieve the file from the very beginning until the file is transferred completely. This is useful for dynamic-ip machines which change their IP addresses quite often, and for sites with very bad internet connectivity.
If you exit lftp when some jobs are not finished yet, lftp will move itself to nohup mode in background. The same happens when you have a real modem hangup or when you close an xterm.
lftp has shell-like command syntax allowing you to launch several commands in parallel in background (&). It is also possible to group commands within () and execute them in background. All background jobs are executed in the same single process. You can bring a foreground job to background with ^Z (c-z) and back with command `wait (or `fg which is alias to `wait). To list running jobs, use command `jobs. Some commands allow redirecting their output (cat, ls, ...) to file or via pipe to external command. Commands can be executed conditionally based on termination status of previous command (&&, ||).
Examples:
lftp> cat file | gzip > file.gz
lftp> get file &
lftp> (cd /path && get file) &
The first command retrieves file from ftp server and passes its contents to gzip which in turn stores compressed data to file.gz. Other commands show how to start commands or command groups in background.
lftp has builtin mirror which can download or update a whole directory tree. There is also reverse mirror (mirror -R) which uploads or updates a directory tree on server.
There is command `at to launch a job at specified time in current context, command `queue to queue commands for sequential execution for current server, and much more.
LFTP supports IPv6 for both FTP and HTTP protocols. For FTP protocol it uses method described in RFC2428.
Other low level stuff supported: ftp proxy, http proxy, ftp over http, opie/skey, fxp transfers, socks.
If lftp was compiled with ssl support, then it includes software developed by the OpenSSL.
Main features:
- FTP and HTTP protocols support.
- FTP (e.g. TIS FWTK) proxy support.
- HTTP proxy support.
- FTP over HTTP proxy support (hftp).
- HTTPS and FTPS protocols support using OpenSSL library.
- Automatic OPIE/SKEY support in FTP protocol.
- FXP transfers support (between two FTP servers, bypassing client machine).
- FTP listings support: unix-style, NT, EPLF.
- Automatic reconnect and retry of an operation on retriable errors or timeout.
- IPv6 support in both FTP and HTTP.
- FISH protocol support. It uses ssh with no special program on server side.
- SFTP protocol v3 and v4 support.
- HTTP/1.1 keep-alive support.
- Experimental support for SRV DNS records.
- SOCKS support (configure option).
- Modification time preservation (if server can report it).
- `reget and `reput support.
- Built-in mirror and reverse mirror (mirror -R).
- Transfer rate throttling for each connection and for all connections in sum.
- Limit for number of connections to the same site. Interruption of background transfer to do a foreground operation when the limit is reached.
- Socket options tuning: buffer size and maximum segment size.
- Job queueing.
- Job execution at specified time.
- Comprehensive scripting support.
- URL recognition in most operations.
- Readline library is used for input.
- Context sensitive completion.
- Bash-like prompt extensions.
- Launching of local shell commands.
- Suspend support.
- Bookmarks.
- Aliases.
- Saving of last directory on each site. `cd - to go there.
- Copying of files between two servers, e.g. between FTP and HTTP.
- Numerous settings which can be associated with a specific server or a group.
- Paging of remote files using external program.
- `zcat and `zmore support.
- Help for commands.
- Command history saved in a file.
- Transfer status includes rate and ETA.
- File listing cache.
- Background jobs (bash-like).
- Job output redirection to a file or to a program via pipe.
- Conditional commands depending on exit status of previous one.
- Loading of binary modules at run time (configure option).
- `pget to download a file using several connections.
- `mirror can download several files in parallel (--parallel option).
- Slots. Each slot is a separate session, switch using Meta-{1-9} or `slot command. Refer to a slot site using pseudo URL slot:name.
Download (1.2MB)
Added: 2007-07-27 License: GPL (GNU General Public License) Price:
536 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above srv search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed