sportmax 006
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 8
FlowScan 1.006
FlowScan is a network analysis and reporting tool. more>>
FlowScan is a network analysis and reporting tool.[ COPYRIGHT=1]
Enhancements:
- The CampusIO and SubNetIO reports were enhanced with a new optional configuration directive: TopN. When defined, this directive causes ``Top Talker reports to be produced. These HTML reports contain the most active (i.e. ``top) source and destination addresses.
- The CampusIO and SubNetIO reports were enhanced to record the number of local IP addresses that where active for each network and subnet into the RRD files. This enables users to estimate the number of active hosts hosts over time, detect ``scans which systematically sweep across network address space, and to calculate the average bytes, packets, and flows per host.
- The template Makefile used to produce the graphs was enhanced to allow the inclusion of ``events in the graphs, similarly to what can be done with Cricket. This allows you to label events such as configuration changes and outages to discover correlations with traffic measurement.
- Two new utilities suitable for stand-alone use, are included. ip2hostname converts IP addresses to their respective hostnames. event2vrule adds ``events to rrdtool graphs.
- Added support for LFAP (Lightweight Flow Accouting Protocol) used by Riverstone and Enterasys (formerly Cabletron) routers. This currently requires slate (from http://www.nmops.org) and lfapd by Steven Premeau . lfapd produces time-stamped raw flow files in the same cflowd-defined format that is processed by FlowScan.
- Added the ability for the CampusIO report to identify outbound flows based solely on the flows destination IP address. While this is less trustworthy than using NextHops or OutputIfIndexes, it is now the default and will be useful for environments where the flow nexthop or output ifIndex values are not meaningful.
- The CampusIO report contains a new experimental feature which reads a BGP routing table, and therefore can determine which Autonomous systems source, transit, or sink most of your institutions traffic. The CampusIO report was enhanced with new optional configuration directives: BGPDumpFile, TopN, ReportPrefixFormat. When properly defined, these directives cause CampusIO to create tabular HTML reports named {origin|path}_{in|out}.html under OutputDir after analyzing each raw flow file. These reports show the ``top Autonomous Systems with which your site exchanges traffic.
- A WebProxyIfIndex directive was added to the CampusIO report. This allows one to specify the index of the interface to which HTTP traffic is being transparently redirected. This enables FlowScan to properly count HTTP flows even though NetFlow v5 does not accurately report the nexthop value for flows which are transparently redirected via a Cisco route-map.
- CampusIO now contains a fix for a bug introduced in FlowScan-1.005 which would sometimes cause perl to abort with this message: patricia.c:645: patricia_lookup: Assertion `prefix failed.
<<lessEnhancements:
- The CampusIO and SubNetIO reports were enhanced with a new optional configuration directive: TopN. When defined, this directive causes ``Top Talker reports to be produced. These HTML reports contain the most active (i.e. ``top) source and destination addresses.
- The CampusIO and SubNetIO reports were enhanced to record the number of local IP addresses that where active for each network and subnet into the RRD files. This enables users to estimate the number of active hosts hosts over time, detect ``scans which systematically sweep across network address space, and to calculate the average bytes, packets, and flows per host.
- The template Makefile used to produce the graphs was enhanced to allow the inclusion of ``events in the graphs, similarly to what can be done with Cricket. This allows you to label events such as configuration changes and outages to discover correlations with traffic measurement.
- Two new utilities suitable for stand-alone use, are included. ip2hostname converts IP addresses to their respective hostnames. event2vrule adds ``events to rrdtool graphs.
- Added support for LFAP (Lightweight Flow Accouting Protocol) used by Riverstone and Enterasys (formerly Cabletron) routers. This currently requires slate (from http://www.nmops.org) and lfapd by Steven Premeau . lfapd produces time-stamped raw flow files in the same cflowd-defined format that is processed by FlowScan.
- Added the ability for the CampusIO report to identify outbound flows based solely on the flows destination IP address. While this is less trustworthy than using NextHops or OutputIfIndexes, it is now the default and will be useful for environments where the flow nexthop or output ifIndex values are not meaningful.
- The CampusIO report contains a new experimental feature which reads a BGP routing table, and therefore can determine which Autonomous systems source, transit, or sink most of your institutions traffic. The CampusIO report was enhanced with new optional configuration directives: BGPDumpFile, TopN, ReportPrefixFormat. When properly defined, these directives cause CampusIO to create tabular HTML reports named {origin|path}_{in|out}.html under OutputDir after analyzing each raw flow file. These reports show the ``top Autonomous Systems with which your site exchanges traffic.
- A WebProxyIfIndex directive was added to the CampusIO report. This allows one to specify the index of the interface to which HTTP traffic is being transparently redirected. This enables FlowScan to properly count HTTP flows even though NetFlow v5 does not accurately report the nexthop value for flows which are transparently redirected via a Cisco route-map.
- CampusIO now contains a fix for a bug introduced in FlowScan-1.005 which would sometimes cause perl to abort with this message: patricia.c:645: patricia_lookup: Assertion `prefix failed.
Download (0.14MB)
Added: 2006-08-05 License: GPL (GNU General Public License) Price:
1179 downloads
Tk::Multi::Manager 1.006
Tk::Multi::Manager is a Tk composite widget managing Tk::Multi slaves. more>>
Tk::Multi::Manager is a Tk composite widget managing Tk::Multi slaves.
SYNOPSIS
use Tk::Multi::Manager ;
use Tk::Multi::Text ; # if you use MultiText as a slave
my $manager = yourWindow -> MultiManager
(
menu => $menu_ref , # optionnal
title => "windows", # optionnal
help => "Explain what your set of widget do" #optionnal
) -> pack ();
# Dont pack it, the managet will do it
my $w1 = $manager -> newSlave
(
type => MultiText,
title => a_label,
help => "Explain what your slave widget does" #optionnal
);
The manager is a composite widget made of a menu cascade of check buttons and slaves which can be Tk::Multi::Text.
The user can add windows to the manager. Each window visibility is controled by a check button in the menu cascade. The check button actually tells the packer to forget the window. note that the window object is not destroyed.
The main menu bar will feature a Help menu on the right. If the main help which explain the purpose of the Multi::Manager and its slaves is provided when creating the widget, the Help sub-menu will feature a global label.
Each slave widget which is created with a help will have its own label in the help menu.
<<lessSYNOPSIS
use Tk::Multi::Manager ;
use Tk::Multi::Text ; # if you use MultiText as a slave
my $manager = yourWindow -> MultiManager
(
menu => $menu_ref , # optionnal
title => "windows", # optionnal
help => "Explain what your set of widget do" #optionnal
) -> pack ();
# Dont pack it, the managet will do it
my $w1 = $manager -> newSlave
(
type => MultiText,
title => a_label,
help => "Explain what your slave widget does" #optionnal
);
The manager is a composite widget made of a menu cascade of check buttons and slaves which can be Tk::Multi::Text.
The user can add windows to the manager. Each window visibility is controled by a check button in the menu cascade. The check button actually tells the packer to forget the window. note that the window object is not destroyed.
The main menu bar will feature a Help menu on the right. If the main help which explain the purpose of the Multi::Manager and its slaves is provided when creating the widget, the Help sub-menu will feature a global label.
Each slave widget which is created with a help will have its own label in the help menu.
Download (0.015MB)
Added: 2006-11-03 License: Perl Artistic License Price:
1091 downloads
IEP-IPP 1.0.006
IEP-IPP project is is a program planning system for managing individual education/program plans for students. more>>
IEP-IPP project is opensource software, and therfore available free of charge. IEP-IPP was designed as a collaborative effort by K-12 special education teachers, multimedia experts, and K-12 technology staff as an effort to produce a high quality and highly functional program planning system for managing individual education/program plans for students in Pre-Kindergarten to grade 12, students in ESL and students in gifted programs. Efforts and suggestions to improve the system are always appreciated.
Main features:
- Web Based, Multiuser
- Goals/Objectives Database
- Email Notifications for student transfers between staff
- School Based management capabilities
- Portable Document Format (PDF) hard copies
- Archives of inactive IPPs
<<lessMain features:
- Web Based, Multiuser
- Goals/Objectives Database
- Email Notifications for student transfers between staff
- School Based management capabilities
- Portable Document Format (PDF) hard copies
- Archives of inactive IPPs
Download (0.95MB)
Added: 2007-06-04 License: GPL (GNU General Public License) Price:
879 downloads
Mail::Box::Parser::C 3.006
Mail::Box::Parser::C is a Perl module that can parse folders for MailBox with C routines. more>>
Mail::Box::Parser::C is a Perl module that can parse folders for MailBox with C routines.
This is an optional module for MailBox, and will (once installed) automatically be used by MailBox to parse e-mail message content when the message is supplied as file-handle. In all other cases, MailBox will use Mail::Box::Parser::Perl.
Mail::Box::Parser::C - reading messages from file using C (XS)
SYNOPSIS
The Mail::Box::Parser::C implements parsing of messages in ANSI C, using Perls XS extension facility.
<<lessThis is an optional module for MailBox, and will (once installed) automatically be used by MailBox to parse e-mail message content when the message is supplied as file-handle. In all other cases, MailBox will use Mail::Box::Parser::Perl.
Mail::Box::Parser::C - reading messages from file using C (XS)
SYNOPSIS
The Mail::Box::Parser::C implements parsing of messages in ANSI C, using Perls XS extension facility.
Download (0.015MB)
Added: 2006-07-06 License: Perl Artistic License Price:
1205 downloads
JDBC Driver for SQLite 006
JDBC Driver for SQLite is a thin layer on top of the SQLite 3.3.x C API. more>>
JDBC Driver for SQLite is a thin layer on top of the SQLite 3.3.x C API. The native JNI library has SQLite compiled into it so all you need to do is include the two files packaged above in your project.
Usage:
Download the binary for the platform you are developing on. Open the tarball and copy the two files into your application directory:
sqlitejdbc.jar
[lib]sqlitejdbc.[dll, so, jnilib]
Reference the driver in your code:
Class.forName("org.sqlite.JDBC");
Connection conn = DriverManager.getConnection("jdbc:sqlite:filename");
// ... use the database ...
conn.close();
And call your program with the drivers JAR file in the classpath and the C library in the librarypath. E.g.
java -cp lib/yourprog.jar:lib/sqlitejdbc.jar
-Djava.library.path=lib
yourprog.Main
Enhancements:
- The driver is now thread-safe and fully supports UTF-16.
- There are binaries for Mac OS, Linux, and Windows, and instructions for compiling with MSVC.
<<lessUsage:
Download the binary for the platform you are developing on. Open the tarball and copy the two files into your application directory:
sqlitejdbc.jar
[lib]sqlitejdbc.[dll, so, jnilib]
Reference the driver in your code:
Class.forName("org.sqlite.JDBC");
Connection conn = DriverManager.getConnection("jdbc:sqlite:filename");
// ... use the database ...
conn.close();
And call your program with the drivers JAR file in the classpath and the C library in the librarypath. E.g.
java -cp lib/yourprog.jar:lib/sqlitejdbc.jar
-Djava.library.path=lib
yourprog.Main
Enhancements:
- The driver is now thread-safe and fully supports UTF-16.
- There are binaries for Mac OS, Linux, and Windows, and instructions for compiling with MSVC.
Download (0.016MB)
Added: 2006-08-05 License: BSD License Price:
705 downloads
Template::Alloy::Parse 1.006
Template::Alloy::Parse is a Perl module with common parsing role for creating AST from templates. more>>
Template::Alloy::Parse is a Perl module with common parsing role for creating AST from templates.
The Template::Alloy::Parse role is reponsible for storing the majority of directive parsing code, as well as for delegating to the TT, HTE, Tmpl, and Velocity roles for finding variables and directives.
ROLE METHODS
parse_tree
Used by load_tree. This is the main grammar engine of the program. It delegates to the syntax found in $self->{SYNTAX} (defaults to alloy) and calls the function found in the $SYNTAX hashref. The majority of these syntaxes use methods found in the $DIRECTIVES hashref to parse different DIRECTIVE types for each particular syntax.
A template that looked like the following:
Foo
[%- GET foo -%]
[%- GET bar -%]
Bar
would parse to the following AST:
[
Foo,
[GET, 6, 15, [foo, 0]],
[GET, 22, 31, [bar, 0]],
Bar,
]
The "GET" words represent the directive used. The 6, 15 represent the beginning and ending characters of the directive in the document. The remaining items are the variables necessary for running the particular directive.
parse_expr
Used to parse a variable, an expression, a literal string, or a number. It returns a parsed variable tree. Samples of parsed variables can be found in the VARIABLE PARSE TREE section.
my $str = "1 + 2 * 3";
my $ast = $self->parse_expr($str);
# $ast looks like [[undef, +, 1, [[undef, *, 2, 3], 0]], 0]
parse_args
Allow for the multitudinous ways that TT parses arguments. This allows for positional as well as named arguments. Named arguments can be separated with a "=" or "=>", and positional arguments should be separated by " " or ",". This only returns an array of parsed variables. To get the actual values, you must call play_expr on each value.
dump_parse_tree
This method allows for returning a string of perl code representing the AST of the parsed tree.
It is mainly used for testing.
dump_parse_expr
This method allows for returning a Data::Dumper dump of a parsed variable. It is mainly used for testing.
parse_*
Methods by these names are used by parse_tree to parse the template. These are the grammar. They are used by all of the various template syntaxes Unless otherwise mentioned, these methods are not exposed via the role.
<<lessThe Template::Alloy::Parse role is reponsible for storing the majority of directive parsing code, as well as for delegating to the TT, HTE, Tmpl, and Velocity roles for finding variables and directives.
ROLE METHODS
parse_tree
Used by load_tree. This is the main grammar engine of the program. It delegates to the syntax found in $self->{SYNTAX} (defaults to alloy) and calls the function found in the $SYNTAX hashref. The majority of these syntaxes use methods found in the $DIRECTIVES hashref to parse different DIRECTIVE types for each particular syntax.
A template that looked like the following:
Foo
[%- GET foo -%]
[%- GET bar -%]
Bar
would parse to the following AST:
[
Foo,
[GET, 6, 15, [foo, 0]],
[GET, 22, 31, [bar, 0]],
Bar,
]
The "GET" words represent the directive used. The 6, 15 represent the beginning and ending characters of the directive in the document. The remaining items are the variables necessary for running the particular directive.
parse_expr
Used to parse a variable, an expression, a literal string, or a number. It returns a parsed variable tree. Samples of parsed variables can be found in the VARIABLE PARSE TREE section.
my $str = "1 + 2 * 3";
my $ast = $self->parse_expr($str);
# $ast looks like [[undef, +, 1, [[undef, *, 2, 3], 0]], 0]
parse_args
Allow for the multitudinous ways that TT parses arguments. This allows for positional as well as named arguments. Named arguments can be separated with a "=" or "=>", and positional arguments should be separated by " " or ",". This only returns an array of parsed variables. To get the actual values, you must call play_expr on each value.
dump_parse_tree
This method allows for returning a string of perl code representing the AST of the parsed tree.
It is mainly used for testing.
dump_parse_expr
This method allows for returning a Data::Dumper dump of a parsed variable. It is mainly used for testing.
parse_*
Methods by these names are used by parse_tree to parse the template. These are the grammar. They are used by all of the various template syntaxes Unless otherwise mentioned, these methods are not exposed via the role.
Download (0.14MB)
Added: 2007-07-14 License: Perl Artistic License Price:
832 downloads
Template::Alloy::VMethod 1.006
Template::Alloy::VMethod is a Perl module with VMethod role. more>>
Template::Alloy::VMethod is a Perl module with VMethod role.
The Template::Alloy::VMethod role provides all of the extra vmethods, filters, and virtual objects that add to the base featureset of Template::Alloy. Most of the vmethods listed here are similar to those provided by Template::Toolkit. We will try to keep Template::Alloys in sync. Template::Alloy also provides several extra methods that are needed for HTML::Template::Expr support.
ROLE METHODS
define_vmethod
Defines a vmethod. See Template::Alloy for more details.
vmethod_*
Methods by these names implement virtual methods that are more complex than oneliners. These methods are not exposed via the role.
filter_*
Methods by these names implement filters that are more complex than one liners. These methods are not exposed via the role.
VIRTUAL METHOD LIST
The following is the list of builtin virtual methods and filters that can be called on each type of data.
In Template::Alloy, the "|" operator can be used to call virtual methods just the same way that the "." operator can. The main difference between the two is that on access to hashrefs or objects, the "|" means to always call the virtual method or filter rather than looking in the hashref for a key by that name, or trying to call that method on the object. This is similar to how TT3 will function.
Virtual methods are also made available via Virtual Objects which are discussed in a later section.
<<lessThe Template::Alloy::VMethod role provides all of the extra vmethods, filters, and virtual objects that add to the base featureset of Template::Alloy. Most of the vmethods listed here are similar to those provided by Template::Toolkit. We will try to keep Template::Alloys in sync. Template::Alloy also provides several extra methods that are needed for HTML::Template::Expr support.
ROLE METHODS
define_vmethod
Defines a vmethod. See Template::Alloy for more details.
vmethod_*
Methods by these names implement virtual methods that are more complex than oneliners. These methods are not exposed via the role.
filter_*
Methods by these names implement filters that are more complex than one liners. These methods are not exposed via the role.
VIRTUAL METHOD LIST
The following is the list of builtin virtual methods and filters that can be called on each type of data.
In Template::Alloy, the "|" operator can be used to call virtual methods just the same way that the "." operator can. The main difference between the two is that on access to hashrefs or objects, the "|" means to always call the virtual method or filter rather than looking in the hashref for a key by that name, or trying to call that method on the object. This is similar to how TT3 will function.
Virtual methods are also made available via Virtual Objects which are discussed in a later section.
Download (0.14MB)
Added: 2007-07-13 License: Perl Artistic License Price:
833 downloads
Template::Alloy::Operator 1.006
Template::Alloy::Operator is a Perl module that provides the regexes necessary for Template::Alloy::Parse to parse operators. more>>
Template::Alloy::Operator is a Perl module that provides the regexes necessary for Template::Alloy::Parse to parse operators and place them in their appropriate precedence.
It also provides the play_operator method which is used by Template::Alloy::Play and Template::Alloy::Compile for playing out the stored operator ASTs.
ROLE METHODS
play_operator
Takes an operator AST in the form of
[undef, +, 1, 2]
Essentially, all operators are stored in RPN notation with a leading "undef" to disabiguate operators in a normal Alloy expression AST.
define_operator
Used for defining new operators.
See Template::Alloy for more details.
<<lessIt also provides the play_operator method which is used by Template::Alloy::Play and Template::Alloy::Compile for playing out the stored operator ASTs.
ROLE METHODS
play_operator
Takes an operator AST in the form of
[undef, +, 1, 2]
Essentially, all operators are stored in RPN notation with a leading "undef" to disabiguate operators in a normal Alloy expression AST.
define_operator
Used for defining new operators.
See Template::Alloy for more details.
Download (0.14MB)
Added: 2007-07-04 License: Perl Artistic License Price:
842 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 sportmax 006 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
