requests
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1296
f2w helpdesk 1.6
f2w helpdesk is helpdesk and knowledge base using a Zope front-end and PostgreSQL back-end. more>>
f2w helpdesk its a helpdesk support system based on requests (some people call them tickets), with a simple web interface. Requests can be classified into categories and assigned a priority.
Categories are associated with specific well-defined problem areas, and f2w helpdesk provides a way to maintain an expert knowledge base of problems and solutions based on request categories.
This is not the place to look for a system that will help you track every minute of your support technicians time. The emphasis is on quickly identifying problems, assigning them to the best person for the job, and helping that person keep track of what needs to be done.
Main features:
- Zope front-end (for rapid development, easy maintenance)
- Your choice of relational DB back-end (whatever Zope supports).
- Semi-intelligent search of contacts from a partial name.
- Expert-system-like question/answer to categorise requests.
- Flexible priority scheme.
- Assignment of requests to individuals or teams.
- E-mail notification sent to person to whom request is assigned.
- Keep working notes on each request, can delete empty notes now.
- Maintain knowledge base about each kind of problem.
- Attach properties (named general-purpose data fields) to categories, so fields for entering them will appear on requests of that category. These can now be checkboxes or selection lists as well as plain text fields.
- Reporting by category, assignee, team, originator, property etc.
- E-mail notification to originator of request.
- User preference for stylesheet.
- User can set an "away until" date, so an operator assigning the requests can know who is available.
- Limited localisation of strings (using a folder of translations for each language - "de", "en", "es", "fr", "hu", "it" and "pl" written so far)
- Request search by various criteria.
- Extract of requests in CSV format, for spreadsheet use.
- Restricted access for non-team members.
<<lessCategories are associated with specific well-defined problem areas, and f2w helpdesk provides a way to maintain an expert knowledge base of problems and solutions based on request categories.
This is not the place to look for a system that will help you track every minute of your support technicians time. The emphasis is on quickly identifying problems, assigning them to the best person for the job, and helping that person keep track of what needs to be done.
Main features:
- Zope front-end (for rapid development, easy maintenance)
- Your choice of relational DB back-end (whatever Zope supports).
- Semi-intelligent search of contacts from a partial name.
- Expert-system-like question/answer to categorise requests.
- Flexible priority scheme.
- Assignment of requests to individuals or teams.
- E-mail notification sent to person to whom request is assigned.
- Keep working notes on each request, can delete empty notes now.
- Maintain knowledge base about each kind of problem.
- Attach properties (named general-purpose data fields) to categories, so fields for entering them will appear on requests of that category. These can now be checkboxes or selection lists as well as plain text fields.
- Reporting by category, assignee, team, originator, property etc.
- E-mail notification to originator of request.
- User preference for stylesheet.
- User can set an "away until" date, so an operator assigning the requests can know who is available.
- Limited localisation of strings (using a folder of translations for each language - "de", "en", "es", "fr", "hu", "it" and "pl" written so far)
- Request search by various criteria.
- Extract of requests in CSV format, for spreadsheet use.
- Restricted access for non-team members.
Download (0.10MB)
Added: 2005-04-20 License: GPL (GNU General Public License) Price:
1649 downloads
Thinux 1.0.1
Thinux is a thin-client cluster server on a Live CD. more>>
Thinux is a thin client system that resides on a Red Hat Linux server. When a thin client requests to boot on LAN, the server will upload the thin client linux system to the thin client. Ideal for lightweight devices such as Point-of-Sales terminals, embedded devices, etc.
<<less Download (36.6MB)
Added: 2005-04-20 License: GPL (GNU General Public License) Price:
1647 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
Netdiscover 0.3 beta6
Netdiscover is a network address discovering tool. more>>
Netdiscover is a network address discovering tool that was developed mainly for those wireless networks without DHCP servers, though it also works on wired networks. It sends ARP requests and sniffs for replies.
<<less Download (0.38MB)
Added: 2005-10-23 License: GPL (GNU General Public License) Price:
1472 downloads
Snowlog 1.1.1
Snowlog is a webserver access log browser/analyzer. more>>
Snowlog is a webserver access log browser/analyzer. It does not generate static reports, but lets you browse through the requests in real time. Filters that accept regular expressions can be applied.
Installation:
make
make install (as root)
<<lessInstallation:
make
make install (as root)
Download (0.029MB)
Added: 2005-10-14 License: GPL (GNU General Public License) Price:
1470 downloads
clsJSPHP 0.1 Alpha
clsJSPHP is a PHP class that allows you to create richer Web applications. more>>
clsJSPHP is a PHP class that allows you to create richer Web applications.
It allows a PHP application to send asynchronous and synchronous requests to a server without reloading the page.
INSTALLATION
Make a reference to the core javascript in the header of your html document: code:
< script src="[PATH_TO_clsJSPHP.php]?jsphp=[PATH_TO_clsJSPHP.php]" language="JavaScript" >< /script >
and you are ready to start!
USAGE
clsJSPHP doesnt register any php functions that you can call with javascript on the client-side. clsJSPHP request a php-file and handle the returned output.
<<lessIt allows a PHP application to send asynchronous and synchronous requests to a server without reloading the page.
INSTALLATION
Make a reference to the core javascript in the header of your html document: code:
< script src="[PATH_TO_clsJSPHP.php]?jsphp=[PATH_TO_clsJSPHP.php]" language="JavaScript" >< /script >
and you are ready to start!
USAGE
clsJSPHP doesnt register any php functions that you can call with javascript on the client-side. clsJSPHP request a php-file and handle the returned output.
Download (0.006MB)
Added: 2005-11-08 License: LGPL (GNU Lesser General Public License) Price:
1445 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
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
Yet Another Object Request Broker 0.2
Yet Another Object Request Broker is an implementation of the CORBA ORB. more>>
Yet Another Object Request Broker is an implementation of the CORBA ORB.
YaOrb advanced installation
YaOrb uses the GNU tools (Autoconf, Automake, ...).
See the GNU documentation for complete instructions, in file $/INSTALL.GNU.
Optional features
The configure script also supports package specific options :
-enable-yoconf=DEV : build in "Development" configuration
-enable-yoconf=TCOV : build in "Coverage" configuration
-enable-yoconf=GPROF : build in "Profiling" configuration
These options are private for the maintainer of this package, and will only work in a specific environment (since assumptions are made about which compiler is used, ...). You may try them, but dont need them to make a build.
The "DEV" (Development) configuration is used to perform a build with all the possible warning options turned on, and warnings are considered errors (using gcc with -Wall -Werror). This configuration is used to enforce that the code is as clean as possible.
The "TCOV" (Coverage) configuration is used to collect code coverage statistics, and also depend on gcc. After running tests, use make profiling to collect code coverage, and read the resulting files :
- $/.SCORE
- $/.MISSING
The "GPROF" (Profiling) configuration is used to collect performance data, and relies on specific gcc options and gprof. After running tests, use make profiling to collect statistics generated.
Enhancements:
- First public release of Yet Another Object Request Broker. Pre alpha, release 0.2
<<lessYaOrb advanced installation
YaOrb uses the GNU tools (Autoconf, Automake, ...).
See the GNU documentation for complete instructions, in file $/INSTALL.GNU.
Optional features
The configure script also supports package specific options :
-enable-yoconf=DEV : build in "Development" configuration
-enable-yoconf=TCOV : build in "Coverage" configuration
-enable-yoconf=GPROF : build in "Profiling" configuration
These options are private for the maintainer of this package, and will only work in a specific environment (since assumptions are made about which compiler is used, ...). You may try them, but dont need them to make a build.
The "DEV" (Development) configuration is used to perform a build with all the possible warning options turned on, and warnings are considered errors (using gcc with -Wall -Werror). This configuration is used to enforce that the code is as clean as possible.
The "TCOV" (Coverage) configuration is used to collect code coverage statistics, and also depend on gcc. After running tests, use make profiling to collect code coverage, and read the resulting files :
- $/.SCORE
- $/.MISSING
The "GPROF" (Profiling) configuration is used to collect performance data, and relies on specific gcc options and gprof. After running tests, use make profiling to collect statistics generated.
Enhancements:
- First public release of Yet Another Object Request Broker. Pre alpha, release 0.2
Download (0.94MB)
Added: 2006-03-01 License: GPL (GNU General Public License) Price:
1332 downloads
pam_userpass 1.0
pam_userpass uses PAM binary prompts to ask the application for the username and password specifically. more>>
PAM has traditionally assumed that services doing authentication have the ability to interact with the user. Unfortunately, this isnt true for services that implement non-interactive and/or fixed protocols, such as FTP and POP3.
This is typically worked around by making the flawed assumption that PAM_PROMPT_ECHO_ON requests the username and PAM_PROMPT_ECHO_OFF requests the password.
With pam_userpass, this assumption is no longer required. pam_userpass uses PAM binary prompts to ask the application for the username and password specifically.
pam_userpass doesnt perform any actual authentication. An actual authentication module should be stacked after pam_userpass and told to use the authentication token (password) provided by pam_userpass.
<<lessThis is typically worked around by making the flawed assumption that PAM_PROMPT_ECHO_ON requests the username and PAM_PROMPT_ECHO_OFF requests the password.
With pam_userpass, this assumption is no longer required. pam_userpass uses PAM binary prompts to ask the application for the username and password specifically.
pam_userpass doesnt perform any actual authentication. An actual authentication module should be stacked after pam_userpass and told to use the authentication token (password) provided by pam_userpass.
Download (0.005MB)
Added: 2006-03-15 License: GPL (GNU General Public License) Price:
1318 downloads
Calamaris 2.99.4.0
Calamaris is a statistics extractor for Squid, NetCache, Oops, and many other proxy-servers. more>>
Calamaris parses logfiles from Squid, NetCache, Inktomi Traffic Server, Oops! proxy server, Novell Internet Caching System, Compaq Tasksmart or iplanet/Netscape Web Proxy Server and generates a report. Written in perl5.
Main features:
Reports:
- Summary
- Peak-usage report
- Request-Method-report (ICP_QUERY, GET, HEAD, ...)
- Status-report of incoming UDP-Requests
- Status-report of incoming TCP-Requests
- Status-report of outgoing Requests
- Status-report of Neighbor-Caches
- report about requested second- or third-level-domains
- report about requested Top-Level-Domains
- Protocol-report (http, gopher, ftp, ...)
- report about requested Content-Types
- report about requested file-extensionen
- report of incoming UDP-requests per Host
- report of incoming TCP-requests per Host
- report of size-based Distribution of Objects
- report about performance in defined timeranges.
- report about the distribution of transaction-times (only V3-beta version)
- report about the distribution of http-errorcodes (only V3-beta version)
- extended report about file-extensions (only V3-beta version)
- more information in the other reports (only V3-beta version)
Other features:
- caching of the parsed data
- HTML-Output
- graphics (only V3-beta version)
- command-line-options
- configuration-file (only V3-beta version)
- GNU Public License
Enhancements:
- HTML-Frame-Report, extended output options, and HTML now supports CSS.
<<lessMain features:
Reports:
- Summary
- Peak-usage report
- Request-Method-report (ICP_QUERY, GET, HEAD, ...)
- Status-report of incoming UDP-Requests
- Status-report of incoming TCP-Requests
- Status-report of outgoing Requests
- Status-report of Neighbor-Caches
- report about requested second- or third-level-domains
- report about requested Top-Level-Domains
- Protocol-report (http, gopher, ftp, ...)
- report about requested Content-Types
- report about requested file-extensionen
- report of incoming UDP-requests per Host
- report of incoming TCP-requests per Host
- report of size-based Distribution of Objects
- report about performance in defined timeranges.
- report about the distribution of transaction-times (only V3-beta version)
- report about the distribution of http-errorcodes (only V3-beta version)
- extended report about file-extensions (only V3-beta version)
- more information in the other reports (only V3-beta version)
Other features:
- caching of the parsed data
- HTML-Output
- graphics (only V3-beta version)
- command-line-options
- configuration-file (only V3-beta version)
- GNU Public License
Enhancements:
- HTML-Frame-Report, extended output options, and HTML now supports CSS.
Download (0.10MB)
Added: 2006-03-20 License: GPL (GNU General Public License) Price:
1314 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
Westhawks Java SNMP stack 5.0
Westhawk SNMP is a lightweight SNMP stack in Java, with Java applet, application, and servlet examples. more>>
Westhawk SNMP is a lightweight SNMP stack in Java, with Java applet, application, and servlet examples.
The stack provides manager functionality for SNMPv1, SNMPv2c, and SNMPv3 (authentication and privacy).
Westhawks Java SNMP stack is capable of sending and receiving PDUs, but has limited agent functionality. The stack supports IPv6.
Enhancements:
- The stack is able to listen for incoming requests (and no longer for traps only).
- The stack is able to listen on multiple ports for requests and traps.
- Contexts (incoming and outgoing) can be bound to a local bind address.
- A separate package stubBrowser4_14.zip that contains a new and experimantal Stub Browser was released.
- Support for DateAndTime text convention was added to AsnOctets.
- A MultiSourcePdu that can do broadcast requests was added.
- Built-in support for IPv6 was added.
- Built-in support for "Reliable SNMP" was added.
<<lessThe stack provides manager functionality for SNMPv1, SNMPv2c, and SNMPv3 (authentication and privacy).
Westhawks Java SNMP stack is capable of sending and receiving PDUs, but has limited agent functionality. The stack supports IPv6.
Enhancements:
- The stack is able to listen for incoming requests (and no longer for traps only).
- The stack is able to listen on multiple ports for requests and traps.
- Contexts (incoming and outgoing) can be bound to a local bind address.
- A separate package stubBrowser4_14.zip that contains a new and experimantal Stub Browser was released.
- Support for DateAndTime text convention was added to AsnOctets.
- A MultiSourcePdu that can do broadcast requests was added.
- Built-in support for IPv6 was added.
- Built-in support for "Reliable SNMP" was added.
Download (1.9MB)
Added: 2006-03-29 License: Freeware Price:
1310 downloads
Apache Intrusion Detection Module 1.0
Apache Intrusion Detection Module is a simple tool to find out intrusion attempts by examining the client requests in real time. more>>
Apache Intrusion Detection Module is a simple tool to find out intrusion attempts by examining the client requests in real time.
This is a simple attempt to build an Intrusion Detection Module for Apache. It is being run at two different sites successfully but there is a performance penalty as the module intercepts all object requests and examines with the list of vulnerable CGI applications.
Issuing a simple make should do in most cases; at worst tweak with the Makefile. The make process will compile mod-id as a apache DSO module, if your server has no DSO support you will need more time...
Any suggestions and improvements are welcome.
<<lessThis is a simple attempt to build an Intrusion Detection Module for Apache. It is being run at two different sites successfully but there is a performance penalty as the module intercepts all object requests and examines with the list of vulnerable CGI applications.
Issuing a simple make should do in most cases; at worst tweak with the Makefile. The make process will compile mod-id as a apache DSO module, if your server has no DSO support you will need more time...
Any suggestions and improvements are welcome.
Download (0.031MB)
Added: 2006-04-04 License: GPL (GNU General Public License) Price:
1304 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
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 requests 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