earmark requests candidates
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1356
Statistics::Candidates 0.9
Candidates is a Perl5 module for manipulating candidate features (help module for Statistics::MaxEntropy). more>>
Candidates is a Perl5 module for manipulating candidate features (help module for Statistics::MaxEntropy).
SYNOPSIS
use Statistics::Candidates;
# create a new candidates object and read candidate features
$candidates = Statistics::Candidates->new($some_file);
# checks for constant candidate features
$candidates->check();
# writes candidates that were not added to a file
$candidates->write($some_other_file);
# clear the administration about being added or not ...
$candidates->clear();
The Candidates object is for storage, retrieval, and manipulation of candidate features.
The reason for separating this code from Maxentropy.pm is that a set of candidate features should be considered a separate object. Blessing them into MaxEntropy would be unnatural.
Also this code is simpler and more stable than that in the MaxEntropy module.
This module requires Bit::SparseVector.
<<lessSYNOPSIS
use Statistics::Candidates;
# create a new candidates object and read candidate features
$candidates = Statistics::Candidates->new($some_file);
# checks for constant candidate features
$candidates->check();
# writes candidates that were not added to a file
$candidates->write($some_other_file);
# clear the administration about being added or not ...
$candidates->clear();
The Candidates object is for storage, retrieval, and manipulation of candidate features.
The reason for separating this code from Maxentropy.pm is that a set of candidate features should be considered a separate object. Blessing them into MaxEntropy would be unnatural.
Also this code is simpler and more stable than that in the MaxEntropy module.
This module requires Bit::SparseVector.
Download (0.041MB)
Added: 2006-11-02 License: Perl Artistic License Price:
1086 downloads
Change Control Request Manager 0.3.0
Change Control Request Manager is an online system for managing change requests for businesses. more>>
Change Control Request Manager is an online system for managing change requests for businesses. Change Control Request Manager project can be customized to fit the needs of a particular business.
Main features:
- Abillity to customize data entry fields. Field type include test, dropdown list, boolean, date, and integer.
- Search for existing CCR records.
- Custom logo. You can place your companys logo at the top.
- Custom Disclaimer message.
- User administration.
- Install script.
Enhancements:
- A reporting system was added.
- Similar to the browse order screen, you can customize the report and display a date range to print.
<<lessMain features:
- Abillity to customize data entry fields. Field type include test, dropdown list, boolean, date, and integer.
- Search for existing CCR records.
- Custom logo. You can place your companys logo at the top.
- Custom Disclaimer message.
- User administration.
- Install script.
Enhancements:
- A reporting system was added.
- Similar to the browse order screen, you can customize the report and display a date range to print.
Download (0.17MB)
Added: 2006-07-21 License: GPL (GNU General Public License) Price:
1193 downloads
Generic Apache Request Library 2.08
Generic Apache Request Libr is a shared library with associated modules for manipulating client request data via the Apache API. more>>
libapreq is a shared library with associated modules for manipulating client request data via the Apache API.
Generic Apache Request Library also includes language bindings for Perl (Apache::Request and Apache::Cookie). Functionality includes:
parsing of application/x-www-form-urlencoded data
parsing of multipart/form-data
parsing of HTTP cookies
Enhancements:
- This release adds some Perl/C API fixes and build improvements.
<<lessGeneric Apache Request Library also includes language bindings for Perl (Apache::Request and Apache::Cookie). Functionality includes:
parsing of application/x-www-form-urlencoded data
parsing of multipart/form-data
parsing of HTTP cookies
Enhancements:
- This release adds some Perl/C API fixes and build improvements.
Download (0.76MB)
Added: 2006-08-11 License: GPL (GNU General Public License) Price:
1169 downloads
Request Tracker 3.6.1
Request Tracker is a web, command-line, and email-based trouble ticketing and bugtracking package. more>>
Request Tracker (RT) is an enterprise-grade ticketing system which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users.
The RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.
<<lessThe RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.
Download (1.2MB)
Added: 2006-09-11 License: GPL (GNU General Public License) Price:
1364 downloads
PITA::XML::Request 0.30
PITA::XML::Request is a request for the testing of a software package. more>>
PITA::XML::Request is a request for the testing of a software package.
SYNOPSIS
# Create a request specification
my $dist = PITA::XML::Request->new(
scheme => perl5,
distname => PITA-XML,
# The package to test
file => PITA::XML::File->new(
filename => Foo-Bar-0.01.tar.gz,
digest => MD5.0123456789ABCDEF0123456789ABCDEF,
),
# Optional fields for repository-based requests
authority => cpan,
authpath => /id/A/AD/ADAMK/Foo-Bar-0.01.tar.gz,
);
PITA::XML::Request is an object for holding information about a request for a distribution to be tested. It is created most often as part of the parsing of a PITA::XML XML file.
It holds the testing scheme, name of the distribition, file information, and authority information (if the distribution was sourced from a repository such as CPAN)
<<lessSYNOPSIS
# Create a request specification
my $dist = PITA::XML::Request->new(
scheme => perl5,
distname => PITA-XML,
# The package to test
file => PITA::XML::File->new(
filename => Foo-Bar-0.01.tar.gz,
digest => MD5.0123456789ABCDEF0123456789ABCDEF,
),
# Optional fields for repository-based requests
authority => cpan,
authpath => /id/A/AD/ADAMK/Foo-Bar-0.01.tar.gz,
);
PITA::XML::Request is an object for holding information about a request for a distribution to be tested. It is created most often as part of the parsing of a PITA::XML XML file.
It holds the testing scheme, name of the distribition, file information, and authority information (if the distribution was sourced from a repository such as CPAN)
Download (0.070MB)
Added: 2007-01-10 License: Perl Artistic License Price:
1017 downloads
Yahoo::Search::Request 1.7.10
Yahoo::Search::Request is a container object for a Yahoo! Search request. more>>
Yahoo::Search::Request is a container object for a Yahoo! Search request. (This package is included in, and automatically loaded by, the Yahoo::Search package.)
Package Use
You never need to use this package directly -- it is loaded automatically by Yahoo::Search.
Object Creation
In practice, this class is generally not dealt with explicitly, but rather implicitly via functions in Yahoo::Search such as Query and Links, which build and use a Request object under the hood.
You also have access to the Request object via Request() method of resulting Response and Result objects.
To be clear, Request objects are created by the Request() method of a Search Engine object (Yahoo::Search).
<<lessPackage Use
You never need to use this package directly -- it is loaded automatically by Yahoo::Search.
Object Creation
In practice, this class is generally not dealt with explicitly, but rather implicitly via functions in Yahoo::Search such as Query and Links, which build and use a Request object under the hood.
You also have access to the Request object via Request() method of resulting Response and Result objects.
To be clear, Request objects are created by the Request() method of a Search Engine object (Yahoo::Search).
Download (0.004MB)
Added: 2006-12-06 License: Perl Artistic License Price:
1052 downloads
CryptNET Password Candidate Generator 1.1.0
CryptNET Password Candidate Generator is a password generator. more>>
CryptNET Password Candidate Generator is a password generator. It generates a list of password candidates for the user to choose from by mapping operating system sources of pseudorandomness into printable character arrays using a mod operation.
It is capable of generating passwords composed of printable characters, alpha numeric characters, alphabetic characters, or numeric only characters.
By default, passgen generates 12 character passwords.
With current grid and cluster computing technology, that is considered the minimum number of characters a password needs in order to be safe from a brute force or dictionay attack.
Enhancements:
- Support for a system wide configuration file is now available, allowing administrators to set defaults that match their local password selection security policies.
- Some minor bug fixes have been made, and some help text formatting improvements have been applied.
- Finally, autotools support has been improved in order to simplify the installation process.
<<lessIt is capable of generating passwords composed of printable characters, alpha numeric characters, alphabetic characters, or numeric only characters.
By default, passgen generates 12 character passwords.
With current grid and cluster computing technology, that is considered the minimum number of characters a password needs in order to be safe from a brute force or dictionay attack.
Enhancements:
- Support for a system wide configuration file is now available, allowing administrators to set defaults that match their local password selection security policies.
- Some minor bug fixes have been made, and some help text formatting improvements have been applied.
- Finally, autotools support has been improved in order to simplify the installation process.
Download (0.058MB)
Added: 2006-12-27 License: Public Domain Price:
1038 downloads
CGI::Request 2.0b1
CGI::Request is a parse client request via a CGI interface. more>>
CGI::Request is a parse client request via a CGI interface.
SYNOPSIS
use CGI::Request;
# Simple interface: (combines SendHeaders, new and import_names)
$req = GetRequest($pkg);
print FmtRequest(); # same as: print $req->as_string
# Full Interface:
$req = new CGI::Request; # fetch and parse request
$field_value = $req->param(FieldName);
@selected = $req->param(SelectMultiField);
@keywords = $req->keywords; # from ISINDEX
print $req->as_string; # format Form and CGI variables
# import form fields into a package as perl variables!
$req->import_names(R);
print "$R::FieldName";
print "@R::SelectMultiField";
@value = $req->param_or($fieldname, $default_return_value);
# Access to CGI interface (see CGI::Base)
$cgi_obj = $req->cgi;
$cgi_var = $req->cgi->var("REMOTE_ADDR");
# Other Functions:
CGI::Request::Interface($cgi); # specify alternative CGI
CGI::Request::Debug($level); # log to STDERR (see CGI::Base)
# Cgi-lib compatibility functions
# use CGI::Request qw(:DEFAULT :cgi-lib); to import them
&ReadParse(*input);
&MethGet;
&PrintHeader;
&PrintVariables(%input);
This module implements the CGI::Request object. This object represents a single query / request / submission from a WWW user. The CGI::Request class understands the concept of HTML forms and fields, specifically how to parse a CGI QUERY_STRING.
<<lessSYNOPSIS
use CGI::Request;
# Simple interface: (combines SendHeaders, new and import_names)
$req = GetRequest($pkg);
print FmtRequest(); # same as: print $req->as_string
# Full Interface:
$req = new CGI::Request; # fetch and parse request
$field_value = $req->param(FieldName);
@selected = $req->param(SelectMultiField);
@keywords = $req->keywords; # from ISINDEX
print $req->as_string; # format Form and CGI variables
# import form fields into a package as perl variables!
$req->import_names(R);
print "$R::FieldName";
print "@R::SelectMultiField";
@value = $req->param_or($fieldname, $default_return_value);
# Access to CGI interface (see CGI::Base)
$cgi_obj = $req->cgi;
$cgi_var = $req->cgi->var("REMOTE_ADDR");
# Other Functions:
CGI::Request::Interface($cgi); # specify alternative CGI
CGI::Request::Debug($level); # log to STDERR (see CGI::Base)
# Cgi-lib compatibility functions
# use CGI::Request qw(:DEFAULT :cgi-lib); to import them
&ReadParse(*input);
&MethGet;
&PrintHeader;
&PrintVariables(%input);
This module implements the CGI::Request object. This object represents a single query / request / submission from a WWW user. The CGI::Request class understands the concept of HTML forms and fields, specifically how to parse a CGI QUERY_STRING.
Download (0.12MB)
Added: 2006-10-21 License: Perl Artistic License Price:
1099 downloads
Pluto Request Action Library 2.0.0.36
Pluto Request Action Library is a library that makes it easy to create a client/server application. more>>
Pluto Request Action Library allows you to create a client/server application, where client sends requests, server replies with responses and optional actions. Very object oriented, and takes only minutes to get going. Same library used for both server & client side.
How does it work?
The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.
The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.
In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.
On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.
<<lessHow does it work?
The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.
The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.
In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.
On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.
Download (0.37MB)
Added: 2006-02-09 License: GPL (GNU General Public License) Price:
1354 downloads
Easy Benchmarking Suite 1.05
Easy Benchmarking Suite is aimed at testing and benchmarking sites. more>>
Easy Benchmarking Suite is aimed at testing and benchmarking sites. Basically, the suite can:
- Issue requests to a URL. A benchmark typically consists of a given number of clients that concurrently issue a number of requests. A request can be any HTTP request (GET, POST, HEAD etc.) with all necessary HTTP header information (session cookies, basic authentication information, etc.);
- Get a quick overview of the results of a benchmark: how many trials succeeded, what are the average times for connecting and processing, what is the standard deviation of these times;
- Prepare a GnuPlot command file so that the obtained results can be plotted.
This document describes the suite. Furthermore, manual pages are provided for the separate parts of the suite: sitebench, sitecollect, and siteplot.
<<less- Issue requests to a URL. A benchmark typically consists of a given number of clients that concurrently issue a number of requests. A request can be any HTTP request (GET, POST, HEAD etc.) with all necessary HTTP header information (session cookies, basic authentication information, etc.);
- Get a quick overview of the results of a benchmark: how many trials succeeded, what are the average times for connecting and processing, what is the standard deviation of these times;
- Prepare a GnuPlot command file so that the obtained results can be plotted.
This document describes the suite. Furthermore, manual pages are provided for the separate parts of the suite: sitebench, sitecollect, and siteplot.
Download (0.14MB)
Added: 2006-03-21 License: Other/Proprietary License Price:
1314 downloads
Jifty::Request 0.60912
Jifty::Request is a canonical internal representation of an incoming Jifty request. more>>
Jifty::Request is a canonical internal representation of an incoming Jifty request.
This document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious.
This class parses the submission and makes it available as a protocol-independent Jifty::Request object.
Each request contains several types of information:
actions
A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects.
state variables
State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information.
continuations
Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation.
(optional) fragments
Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion.
<<lessThis document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious.
This class parses the submission and makes it available as a protocol-independent Jifty::Request object.
Each request contains several types of information:
actions
A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects.
state variables
State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information.
continuations
Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation.
(optional) fragments
Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion.
Download (0.52MB)
Added: 2006-10-20 License: Perl Artistic License Price:
1099 downloads
mod_rssindex 1.0
mod_rssindex creates a non-recursive RSS 2.0 feed of the directory contained in the HTTP Request. more>>
mod_rssindex is an Apache module which creates a non-recursive RSS 2.0 feed of the directory contained in the HTTP Request.
<<less Download (0.010MB)
Added: 2006-04-28 License: GPL (GNU General Public License) Price:
1274 downloads
GalleryMaster 0.1
GalleryMaster is a PHP script for viewing slideshows. more>>
GalleryMaster is a PHP script for viewing slideshows. GalleryMaster is far from complete, but Im working on it when Im not studying or dating.
If you want to contribute to the project, then download the source. All sorts of feature requests are welcome.
Main features:
- Displays images of any format that your browser can handle
- Supports directory listing
- Intelligent gallery detection
<<lessIf you want to contribute to the project, then download the source. All sorts of feature requests are welcome.
Main features:
- Displays images of any format that your browser can handle
- Supports directory listing
- Intelligent gallery detection
Download (0.009MB)
Added: 2006-05-03 License: GPL (GNU General Public License) Price:
1269 downloads
JustAjax Table 0.7
JustAjax Table project performs all operation with tables on-fly using Ajax requests. more>>
JustAjax Table project performs all operation with tables "on-fly" using Ajax requests.
Main features:
- Supports all popular web browsers.
- Populates the data into the cells automatically .
- On-fly scrolling, sorting, editing.
- PHP/MySQL backend.
- Works with up to 100,000 record tables.
<<lessMain features:
- Supports all popular web browsers.
- Populates the data into the cells automatically .
- On-fly scrolling, sorting, editing.
- PHP/MySQL backend.
- Works with up to 100,000 record tables.
Download (0.040MB)
Added: 2007-06-08 License: Other/Proprietary License Price:
869 downloads
Fortress 0.3
Fortress is a simple script driven framework for performing security scans. more>>
Fortress is a simple script driven framework for performing security scans. The core of the application is an application which will execute testing scripts written using the embedded LUA scripting engine.
The scripts may perform almost arbitrary operations, including making HTTP requests, conducting port scanning, and taking advantage of several other provided primitives.
<<lessThe scripts may perform almost arbitrary operations, including making HTTP requests, conducting port scanning, and taking advantage of several other provided primitives.
Download (0.076MB)
Added: 2005-10-26 License: GPL (GNU General Public License) Price:
1478 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above earmark requests candidates 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