http dav 0.31
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2361
HTTP::DAV 0.31
HTTP::DAV is a WebDAV client library for Perl5. more>>
HTTP::DAV is a WebDAV client library for Perl5.
SYNOPSIS
# DAV script that connects to a webserver, safely makes
# a new directory and uploads all html files in
# the /tmp directory.
use HTTP::DAV;
$d = new HTTP::DAV;
$url = "http://host.org:8080/dav/";
$d->credentials( -user=>"pcollins",-pass =>"mypass",
-url =>$url, -realm=>"DAV Realm" );
$d->open( -url=>"$url )
or die("Couldnt open $url: " .$d->message . "n");
# Make a null lock on newdir
$d->lock( -url => "$url/newdir", -timeout => "10m" )
or die "Wont put unless I can lock for 10 minutesn";
# Make a new directory
$d->mkcol( -url => "$url/newdir" )
or die "Couldnt make newdir at $urln";
# Upload multiple files to newdir.
if ( $d->put( -local => "/tmp/*.html", -url => $url ) ) {
print "successfully uploaded multiple files to $urln";
} else {
print "put failed: " . $d->message . "n";
}
$d->unlock( -url => $url );
Main features:
- Full RFC2518 method support. OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK.
- A fully object-oriented API.
- Recursive GET and PUT for site backups and other scripted transfers.
- Transparent lock handling when performing LOCK/COPY/UNLOCK sequences.
- http and https support (https requires the Crypt::SSLeay library). See INSTALLATION.
- Basic AND Digest authentication support (Digest auth requires the MD5 library). See INSTALLATION.
- dave, a fully-functional ftp-style interface written on top of the HTTP::DAV API and bundled by default with the HTTP::DAV library. (If youve already installed HTTP::DAV, then dave will also have been installed (probably into /usr/local/bin). You can see its man page by typing "perldoc dave" or going to http://www.webdav.org/perldav/dave/.
- It is built on top of the popular LWP (Library for WWW access in Perl). This means that HTTP::DAV inherits proxy support, redirect handling, basic (and digest) authorization and many other HTTP operations. See LWP for more information.
- Popular server support. HTTP::DAV has been tested against the following servers: mod_dav, IIS5, Xythos webfile server and mydocsonline. The library is growing an impressive interoperability suite which also serves as useful "sample scripts". See "make test" and t/*.
<<lessSYNOPSIS
# DAV script that connects to a webserver, safely makes
# a new directory and uploads all html files in
# the /tmp directory.
use HTTP::DAV;
$d = new HTTP::DAV;
$url = "http://host.org:8080/dav/";
$d->credentials( -user=>"pcollins",-pass =>"mypass",
-url =>$url, -realm=>"DAV Realm" );
$d->open( -url=>"$url )
or die("Couldnt open $url: " .$d->message . "n");
# Make a null lock on newdir
$d->lock( -url => "$url/newdir", -timeout => "10m" )
or die "Wont put unless I can lock for 10 minutesn";
# Make a new directory
$d->mkcol( -url => "$url/newdir" )
or die "Couldnt make newdir at $urln";
# Upload multiple files to newdir.
if ( $d->put( -local => "/tmp/*.html", -url => $url ) ) {
print "successfully uploaded multiple files to $urln";
} else {
print "put failed: " . $d->message . "n";
}
$d->unlock( -url => $url );
Main features:
- Full RFC2518 method support. OPTIONS, TRACE, GET, HEAD, DELETE, PUT, COPY, MOVE, PROPFIND, PROPPATCH, LOCK, UNLOCK.
- A fully object-oriented API.
- Recursive GET and PUT for site backups and other scripted transfers.
- Transparent lock handling when performing LOCK/COPY/UNLOCK sequences.
- http and https support (https requires the Crypt::SSLeay library). See INSTALLATION.
- Basic AND Digest authentication support (Digest auth requires the MD5 library). See INSTALLATION.
- dave, a fully-functional ftp-style interface written on top of the HTTP::DAV API and bundled by default with the HTTP::DAV library. (If youve already installed HTTP::DAV, then dave will also have been installed (probably into /usr/local/bin). You can see its man page by typing "perldoc dave" or going to http://www.webdav.org/perldav/dave/.
- It is built on top of the popular LWP (Library for WWW access in Perl). This means that HTTP::DAV inherits proxy support, redirect handling, basic (and digest) authorization and many other HTTP operations. See LWP for more information.
- Popular server support. HTTP::DAV has been tested against the following servers: mod_dav, IIS5, Xythos webfile server and mydocsonline. The library is growing an impressive interoperability suite which also serves as useful "sample scripts". See "make test" and t/*.
Download (0.075MB)
Added: 2007-07-20 License: Perl Artistic License Price:
826 downloads
lns.http 0.1
lns.http is a simple framework for writing Common LISP Web applications. more>>
lns.http is a simple framework for writing Common Lisp web applications. The project handles the incoming connections, parses HTTP headers and queries, and finally hands control over to your URL handler.
lns.http is a HTTP/1.1 compatible web server but tries to achieve compatibility with lesser (down to the informal HTTP/0.9) clients.
The lns.http web server uses lisp-network-server to take care of network handling.
This software is licensed unter the LGPL.
<<lesslns.http is a HTTP/1.1 compatible web server but tries to achieve compatibility with lesser (down to the informal HTTP/0.9) clients.
The lns.http web server uses lisp-network-server to take care of network handling.
This software is licensed unter the LGPL.
Download (0.017MB)
Added: 2006-12-19 License: LGPL (GNU Lesser General Public License) Price:
1046 downloads
Monkey HTTP Daemon 0.9.1
Monkey is a Web server written in C that works under Linux. more>>
Monkey is a Web server written in C that works under Linux. This is an open source project based on the HTTP/1.1 protocol.
The objective is to develop a fast, efficient, small and easy to configure web server. If you wish to contribute to this project as a beta-tester, submitting suggestions and constructive criticisms, just contact me. Your input is welcome.
Main features:
- Get, Post & Head method
- CGI & PHP
- Multithreading
- Config files
- Mime types
- VirtualHost
- Directories navigation
- Users home
- Deny by URL & IP
- Resume
<<lessThe objective is to develop a fast, efficient, small and easy to configure web server. If you wish to contribute to this project as a beta-tester, submitting suggestions and constructive criticisms, just contact me. Your input is welcome.
Main features:
- Get, Post & Head method
- CGI & PHP
- Multithreading
- Config files
- Mime types
- VirtualHost
- Directories navigation
- Users home
- Deny by URL & IP
- Resume
Download (0.082MB)
Added: 2005-09-05 License: GPL (GNU General Public License) Price:
1510 downloads
Tabble 0.31
Tabble is a small alternative X shell which presents your programs in tabs for easy launch. more>>
Tabble is a small alternative X shell which presents your programs in tabs for easy launch. Tabble is not meant to replace a window manager, just complement it. Light window managers benefit the most from tabble.
The idea is that tabble is always on top so multiple launches can be made without re-navigating a menu hierarchy or clearing the desktop.
The above window, customized to your choices, can appear at a fixed position on your screen so you can spawn a few things quickly. Hit the hide button and its out of your way, and the next switch to tabble will be faster.
One of the reasons for tabble is that it can be started from within a chroot (32 bit inside 64 say). Other programs within the chroot can be easily spawned from this tabble.
KDE/GNOME could use this concept but there is still a case for a standalone program for those who switch between window managers - because only one configuration file needs maintaining and it can be shared.
<<lessThe idea is that tabble is always on top so multiple launches can be made without re-navigating a menu hierarchy or clearing the desktop.
The above window, customized to your choices, can appear at a fixed position on your screen so you can spawn a few things quickly. Hit the hide button and its out of your way, and the next switch to tabble will be faster.
One of the reasons for tabble is that it can be started from within a chroot (32 bit inside 64 say). Other programs within the chroot can be easily spawned from this tabble.
KDE/GNOME could use this concept but there is still a case for a standalone program for those who switch between window managers - because only one configuration file needs maintaining and it can be shared.
Download (0.092MB)
Added: 2006-04-27 License: GPL (GNU General Public License) Price:
1275 downloads
HTTP::Webdav 0.1.18-0.17.1
HTTP::Webdav is a Perl interface to Neon HTTP and WebDAV client library. more>>
HTTP::Webdav is a Perl interface to Neon HTTP and WebDAV client library.
SYNOPSIS
use HTTP::Webdav ;
$sess = HTTP::Webdav -> new ;
$sess -> server ("www.ecos.de", 80) ;
$sess -> get ("/", STDOUT) ;
$sess -> put ("/dav/foo.htm", STDIN) ;
# remove property test3
# set value of property test to bar
@props = (
{ name => {nspace => DAV:, name => test3}, type => 1},
{ name => {nspace => DAV:, name => test}, value => bar},
) ;
$sess -> proppatch ("/dav/foo.htm", @props) ;
sub iterator
{
my ($userdata, $propname, $propvalue, $propstatus) = @_ ;
print "propfind userdata = $userdata nspace = $propname->{nspace} name = $propname->{name} value = $propvaluen" ;
return 0 ;
}
sub callback
{
my ($userdata, $href, $results) = @_ ;
print "propfind callback userdata = $userdata href = $hrefn" ;
$results -> iterate (&iterator) ;
}
$sess -> simple_propfind ("/dav", NE_DEPTH_ONE, undef, &callback) ;
print "Status: ", $sess -> get_error , "n" ;
The neon API is encapsultated in a number of Perl classes. Everything that doesnt fit in a class has gone to HTTP::Webdav::Util. (Maybe some of these function will move to other classes in the future)
The clases are
HTTP::Webdav
Main class which holds a http session
HTTP::Webdav::MultiStatus
Class to handle 207 responses
HTTP::Webdav::Hip
Interface to XML parser for properties
HTTP::Webdav::Lock
Holds a lock
HTTP::Webdav::LockSession
Holds a lock session
HTTP::Webdav::Propfind
Class to access the result of a PROPFIND
HTTP::Webdav::Propset
Class to acess properties of one resource
HTTP::Webdav::Request
Low level interface to http request
HTTP::Webdav::MD5
MD5 checksum
HTTP::Webdav::SSL
SSL support
HTTP::Webdav::Socket
Low level socket access
WARNING: This wrapper is alpha code, while neon is around for some time and stable to use, not all of the interface functions provided by this Perl module has been tested extensivly, but most of them should work without problems (At least they do it for me).
<<lessSYNOPSIS
use HTTP::Webdav ;
$sess = HTTP::Webdav -> new ;
$sess -> server ("www.ecos.de", 80) ;
$sess -> get ("/", STDOUT) ;
$sess -> put ("/dav/foo.htm", STDIN) ;
# remove property test3
# set value of property test to bar
@props = (
{ name => {nspace => DAV:, name => test3}, type => 1},
{ name => {nspace => DAV:, name => test}, value => bar},
) ;
$sess -> proppatch ("/dav/foo.htm", @props) ;
sub iterator
{
my ($userdata, $propname, $propvalue, $propstatus) = @_ ;
print "propfind userdata = $userdata nspace = $propname->{nspace} name = $propname->{name} value = $propvaluen" ;
return 0 ;
}
sub callback
{
my ($userdata, $href, $results) = @_ ;
print "propfind callback userdata = $userdata href = $hrefn" ;
$results -> iterate (&iterator) ;
}
$sess -> simple_propfind ("/dav", NE_DEPTH_ONE, undef, &callback) ;
print "Status: ", $sess -> get_error , "n" ;
The neon API is encapsultated in a number of Perl classes. Everything that doesnt fit in a class has gone to HTTP::Webdav::Util. (Maybe some of these function will move to other classes in the future)
The clases are
HTTP::Webdav
Main class which holds a http session
HTTP::Webdav::MultiStatus
Class to handle 207 responses
HTTP::Webdav::Hip
Interface to XML parser for properties
HTTP::Webdav::Lock
Holds a lock
HTTP::Webdav::LockSession
Holds a lock session
HTTP::Webdav::Propfind
Class to access the result of a PROPFIND
HTTP::Webdav::Propset
Class to acess properties of one resource
HTTP::Webdav::Request
Low level interface to http request
HTTP::Webdav::MD5
MD5 checksum
HTTP::Webdav::SSL
SSL support
HTTP::Webdav::Socket
Low level socket access
WARNING: This wrapper is alpha code, while neon is around for some time and stable to use, not all of the interface functions provided by this Perl module has been tested extensivly, but most of them should work without problems (At least they do it for me).
Download (0.032MB)
Added: 2007-08-15 License: Perl Artistic License Price:
809 downloads
Dwarf HTTP Server 1.3.1
Dwarf HTTP Server is a full-featured and ready-to-use web server with the Java Servlet API 2.2 and Java Server Pages 1.1. more>>
Dwarf HTTP Server is a full-featured and ready-to-use web server with the Java Servlet API 2.2 and Java Server Pages 1.1 implementation.
Dwarf HTTP Server can be used either standalone or embed in a larger hosting application, free of charge for the binary redistribution
Since the server is based on the Dwarf framework, it shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- multi-threaded design
- dynamically adjusted number of active threads
- Java Servlet API 2.2 implementation
- Java Server Pages 1.1 (by Apache Tomcat/Jasper)
- HTTP/1.1 and CGI/1.1 implementation
- WebDAV Class 1 implementation
- built-in SSL/TLS support
- IP-based and name-based virtual hosts
- customizable authentication and authorization
- standard and custom HTTP log formats
- extensible session management
- Basic and Form-based HTTP authentication
- automatic deploying of WAR archives
- runtime server configuration
- full documentation with guides and tutorials
- web application examples with source code
<<lessDwarf HTTP Server can be used either standalone or embed in a larger hosting application, free of charge for the binary redistribution
Since the server is based on the Dwarf framework, it shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- multi-threaded design
- dynamically adjusted number of active threads
- Java Servlet API 2.2 implementation
- Java Server Pages 1.1 (by Apache Tomcat/Jasper)
- HTTP/1.1 and CGI/1.1 implementation
- WebDAV Class 1 implementation
- built-in SSL/TLS support
- IP-based and name-based virtual hosts
- customizable authentication and authorization
- standard and custom HTTP log formats
- extensible session management
- Basic and Form-based HTTP authentication
- automatic deploying of WAR archives
- runtime server configuration
- full documentation with guides and tutorials
- web application examples with source code
Download (0.91MB)
Added: 2005-12-08 License: Freely Distributable Price:
1415 downloads
HTTP Grabber 1.0
HTTP grabber can be used to see what other people on your LAN are downloading. more>>
HTTP grabber can be used to see what other people on your LAN are downloading as it saves information being sent via the HTTP protocol to disk.
Check the makefile:
if libngrep isnt in /usr/local/lib, change the LFLAGS
if you dont want httpgrabber to be installed in /usr/local/bin, change the directory in the "install" rule.
To install just run "make" and "make install"
<<lessCheck the makefile:
if libngrep isnt in /usr/local/lib, change the LFLAGS
if you dont want httpgrabber to be installed in /usr/local/bin, change the directory in the "install" rule.
To install just run "make" and "make install"
Download (0.007MB)
Added: 2006-06-28 License: BSD License Price:
1220 downloads
HTTP::Async 0.05
HTTP::Async is a Perl module that can process multiple HTTP requests in parallel without blocking. more>>
HTTP::Async is a Perl module that can process multiple HTTP requests in parallel without blocking.
SYNOPSIS
Create an object and add some requests to it:
use HTTP::Async;
my $async = HTTP::Async->new;
# create some requests and add them to the queue.
$async->add( HTTP::Request->new( GET => http://www.perl.org/ ) );
$async->add( HTTP::Request->new( GET => http://www.ecclestoad.co.uk/ ) );
and then EITHER process the responses as they come back:
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
OR do something else if there is no response ready:
while ( $async->not_empty ) {
if ( my $response = $async->next_response ) {
# deal with $response
} else {
# do something else
{
}
OR just use the async object to fetch stuff in the background and deal with the responses at the end.
# Do some long code...
for ( 1 .. 100 ) {
some_function();
$async->poke; # lets it check for incoming data.
}
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
Although using the conventional LWP::UserAgent is fast and easy it does have some drawbacks - the code execution blocks until the request has been completed and it is only possible to process one request at a time. HTTP::Async attempts to address these limitations.
It gives you a Async object that you can add requests to, and then get the requests off as they finish. The actual sending and receiving of the requests is abstracted. As soon as you add a request it is transmitted, if there are too many requests in progress at the moment they are queued. There is no concept of starting or stopping - it runs continuously.
Whilst it is waiting to receive data it returns control to the code that called it meaning that you can carry out processing whilst fetching data from the network. All without forking or threading - it is actually done using select lists.
<<lessSYNOPSIS
Create an object and add some requests to it:
use HTTP::Async;
my $async = HTTP::Async->new;
# create some requests and add them to the queue.
$async->add( HTTP::Request->new( GET => http://www.perl.org/ ) );
$async->add( HTTP::Request->new( GET => http://www.ecclestoad.co.uk/ ) );
and then EITHER process the responses as they come back:
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
OR do something else if there is no response ready:
while ( $async->not_empty ) {
if ( my $response = $async->next_response ) {
# deal with $response
} else {
# do something else
{
}
OR just use the async object to fetch stuff in the background and deal with the responses at the end.
# Do some long code...
for ( 1 .. 100 ) {
some_function();
$async->poke; # lets it check for incoming data.
}
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
Although using the conventional LWP::UserAgent is fast and easy it does have some drawbacks - the code execution blocks until the request has been completed and it is only possible to process one request at a time. HTTP::Async attempts to address these limitations.
It gives you a Async object that you can add requests to, and then get the requests off as they finish. The actual sending and receiving of the requests is abstracted. As soon as you add a request it is transmitted, if there are too many requests in progress at the moment they are queued. There is no concept of starting or stopping - it runs continuously.
Whilst it is waiting to receive data it returns control to the code that called it meaning that you can carry out processing whilst fetching data from the network. All without forking or threading - it is actually done using select lists.
Download (0.015MB)
Added: 2007-01-17 License: Perl Artistic License Price:
1011 downloads
HTTP::Handle 0.2
HTTP::Handle is a HTTP Class designed for streaming. more>>
HTTP::Handle is a HTTP Class designed for streaming.
SYNOPSIS
use HTTP::Handle;
my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();
my $fd = $http->fd();
while () {
print "--> $_";
}
The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.
HTTP::Handle->new()
Create a new HTTP::Handle object thingy.
Arguments possible:
url => "http://www.google.com/"
Sets the initial URL to connect to.
follow_redirects => [ 0 | 1 ]
Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.
http_request => HASHREF
Any thing put in here will be sent as "key: value" in the http request string.
$http->connect()
Connect, send the http request, and process the response headers.
This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.
$http->fd()
Get the file descriptor (socket) were using to connect.
$http->url( [ url_string ])
Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the
$http->follow_redirects( [ 0 | 1 ] )
If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.
Defaults to 1 (will follow redirects).
$http->http_request_string()
Returns a string containing the HTTP request and headers, this is used when
$http->connect() is called.
<<lessSYNOPSIS
use HTTP::Handle;
my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();
my $fd = $http->fd();
while () {
print "--> $_";
}
The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.
HTTP::Handle->new()
Create a new HTTP::Handle object thingy.
Arguments possible:
url => "http://www.google.com/"
Sets the initial URL to connect to.
follow_redirects => [ 0 | 1 ]
Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.
http_request => HASHREF
Any thing put in here will be sent as "key: value" in the http request string.
$http->connect()
Connect, send the http request, and process the response headers.
This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.
$http->fd()
Get the file descriptor (socket) were using to connect.
$http->url( [ url_string ])
Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the
$http->follow_redirects( [ 0 | 1 ] )
If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.
Defaults to 1 (will follow redirects).
$http->http_request_string()
Returns a string containing the HTTP request and headers, this is used when
$http->connect() is called.
Download (0.005MB)
Added: 2006-11-16 License: Perl Artistic License Price:
1072 downloads
MP3c 0.31
MP3c is a special program for converting audio-cds to mp3/ogg-format. more>>
MP3c is a special program for converting audio-cds to ogg/mp3-format. It is a frontend for every grab-program and mp3-encoder. Nearly every program should be supported. MP3c has two different run-modes: An interactive mode with a menu-enviroment (based on curses-lib), which can used on textconsoles as well under X11, and a batchmode, which allows automatic encoding of cds inside shellscripts (eg at night within cronjobs).
There are two different possibilities for encoding (depends on your ripper and encoder): Non-Fly encoding, where an audio-track is first grabbed from cds and then encoded, and On-Fly encoding, where grabbing and encoding is one step. Normally you should refer to Non-Fly encoding, since your cdrom-drive hasnt to work all the time, and some encoder produces a "click" at the beginning of mp3/ogg-files if On-Fly encoding is used. The only disadvantage of Non-Fly encoding is, that there is a temp-file, which can grow up to 50-100 MB sometimes.
Information about songtitle on your cds are received with help of CDDB database. In contrast to other programs, an CDDB-entry is detailed analyzed to find every information even for sampler-cds.
Creation of filenames is userdefined. You can use pattern to constitute the appearance of your mp3-files individually. Furthermore you can decide how spaces within filenames should be handled (you can allow them, convert them to underscores "_" or just kill them).
Interessting is the possibility of shellscript creation, which contains all functionality for encoding your cds. You can start these scripts as daemon-processes or run them at night inside a cronjob.
Recommended programs for the use of MP3c are: CDparanoia as audio-cd grabber, Encoder as MP3-encoder and MP3info for creating MP3-ID-tags. For OGG use oggenc. If you need, you can download these programs here, or a complete package with these programs inside. Furthermore you can download runable binaries, but only for glibc 2.1 (linux i386) at the moment. If you like to create RPMs and/or binaries for other systems and libraries, please send these to me, so that I can put it on my page.
Enhancements:
- Switched to CDDB protocol level 5 to support detection and saving of year and genre information.
<<lessThere are two different possibilities for encoding (depends on your ripper and encoder): Non-Fly encoding, where an audio-track is first grabbed from cds and then encoded, and On-Fly encoding, where grabbing and encoding is one step. Normally you should refer to Non-Fly encoding, since your cdrom-drive hasnt to work all the time, and some encoder produces a "click" at the beginning of mp3/ogg-files if On-Fly encoding is used. The only disadvantage of Non-Fly encoding is, that there is a temp-file, which can grow up to 50-100 MB sometimes.
Information about songtitle on your cds are received with help of CDDB database. In contrast to other programs, an CDDB-entry is detailed analyzed to find every information even for sampler-cds.
Creation of filenames is userdefined. You can use pattern to constitute the appearance of your mp3-files individually. Furthermore you can decide how spaces within filenames should be handled (you can allow them, convert them to underscores "_" or just kill them).
Interessting is the possibility of shellscript creation, which contains all functionality for encoding your cds. You can start these scripts as daemon-processes or run them at night inside a cronjob.
Recommended programs for the use of MP3c are: CDparanoia as audio-cd grabber, Encoder as MP3-encoder and MP3info for creating MP3-ID-tags. For OGG use oggenc. If you need, you can download these programs here, or a complete package with these programs inside. Furthermore you can download runable binaries, but only for glibc 2.1 (linux i386) at the moment. If you like to create RPMs and/or binaries for other systems and libraries, please send these to me, so that I can put it on my page.
Enhancements:
- Switched to CDDB protocol level 5 to support detection and saving of year and genre information.
Download (0.20MB)
Added: 2006-07-30 License: GPL (GNU General Public License) Price:
1184 downloads
HTTP::GetImages 0.343
HTTP::GetImages is a spider to recover and store images from web pages. more>>
HTTP::GetImages is a spider to recover and store images from web pages.
SYNOPSIS
use HTTP::GetImages;
$_ = new HTTP::GetImages (
dir => .,
todo => [http://www.google.com/,],
dont => [http://www.somewhere/ignorethis.html,http://and.this.html],
chat => 1,
);
$_->print_imgs;
$_->print_done;
$_->print_failed;
$_->print_ignored;
my $hash = $_->imgs_as_hash;
foreach (keys %{$hash}){
warn "$_ = ",$hash->{$_},"n";
}
exit;
This module allow syou to automate the searching, recovery and local storage of images from the web, including those linked by anchor (A), mage (IMG) and image map (AREA) elements.
Supply a URI or list of URIs to process, and HTTP::GetImages will recurse over every link it finds, searching for images.
By supplying a list of URIs, you can restrict the search to certain webservers and directories, or exclude it from certain webservers and directories.
You can also decide to reject images that are too small or too large.
<<lessSYNOPSIS
use HTTP::GetImages;
$_ = new HTTP::GetImages (
dir => .,
todo => [http://www.google.com/,],
dont => [http://www.somewhere/ignorethis.html,http://and.this.html],
chat => 1,
);
$_->print_imgs;
$_->print_done;
$_->print_failed;
$_->print_ignored;
my $hash = $_->imgs_as_hash;
foreach (keys %{$hash}){
warn "$_ = ",$hash->{$_},"n";
}
exit;
This module allow syou to automate the searching, recovery and local storage of images from the web, including those linked by anchor (A), mage (IMG) and image map (AREA) elements.
Supply a URI or list of URIs to process, and HTTP::GetImages will recurse over every link it finds, searching for images.
By supplying a list of URIs, you can restrict the search to certain webservers and directories, or exclude it from certain webservers and directories.
You can also decide to reject images that are too small or too large.
Download (0.007MB)
Added: 2006-11-15 License: GPL (GNU General Public License) Price:
1073 downloads
qmail-smtpd-auth 0.31
qmail-smtpd-auth is a patch for qmail that enables it to support SMTP AUTH protocol. more>>
qmail-smtpd-auth is a patch for qmail that enables it to support SMTP AUTH protocol with the following auth types: LOGIN, PLAIN and CRAM-MD5. Its based on a previous patch by Mrs.Brisby that implemented LOGIN type. This version has some enhancements and allows easy adding of new auth methods.
If you want to learn more about SMTP AUTH itself, then visit my SMTP AUTH page.
This patch adds the ESMTP AUTH option to qmail-1.03, allowing the LOGIN, PLAIN, and CRAM-MD5 AUTH types. An appropriate checkpassword tool is necessary to support the authentication. See http://cr.yp.to/checkpwd.html for more information on the interface. Note that the checkpassword tool should support all of the AUTH types
advertised by qmail-smtpd.
As reflected in the modified qmail-smtpd(8) man page, qmail-smtpd must be invoked with three arguments: hostname, checkprogram, and subprogram. If these arguments are missing, qmail-smtpd will still advertise availability of AUTH, but will fail with a permanent error when AUTH is used.
hostname is simply used to form the CRAM-MD5 challenge. qmail-smtpd invokes checkprogram, feeding it the username and password, in the case of LOGIN or PLAIN, or the username, challenge, and response, in the case of CRAM-MD5. If the user is permitted, checkprogram invokes subprogram, which just has to exit with a status of 0 for the user to be authenticated. Otherwise, checkprogram exits with a non-zero
status. subprogram can usually be /usr/bin/true (or /bin/true, depending on your flavor of OS).
If the user is successfully authenticated, the RELAYCLIENT environment variable is effectively set for the SMTP session, and the TCPREMOTEINFO environment variable is set to the authenticated username, overriding any value that tcpserver may have set. The
value of TCPREMOTEINFO is reflected in a Received header.
Enhancements:
- bug: AUTH PLAIN 334 response not RFC compliant. Reported by Mark Crispin
- .
- change: Set TCPREMOTEINFO environment variable to authenticated username. (Previously only set locally to qmail-smtpd.)
<<lessIf you want to learn more about SMTP AUTH itself, then visit my SMTP AUTH page.
This patch adds the ESMTP AUTH option to qmail-1.03, allowing the LOGIN, PLAIN, and CRAM-MD5 AUTH types. An appropriate checkpassword tool is necessary to support the authentication. See http://cr.yp.to/checkpwd.html for more information on the interface. Note that the checkpassword tool should support all of the AUTH types
advertised by qmail-smtpd.
As reflected in the modified qmail-smtpd(8) man page, qmail-smtpd must be invoked with three arguments: hostname, checkprogram, and subprogram. If these arguments are missing, qmail-smtpd will still advertise availability of AUTH, but will fail with a permanent error when AUTH is used.
hostname is simply used to form the CRAM-MD5 challenge. qmail-smtpd invokes checkprogram, feeding it the username and password, in the case of LOGIN or PLAIN, or the username, challenge, and response, in the case of CRAM-MD5. If the user is permitted, checkprogram invokes subprogram, which just has to exit with a status of 0 for the user to be authenticated. Otherwise, checkprogram exits with a non-zero
status. subprogram can usually be /usr/bin/true (or /bin/true, depending on your flavor of OS).
If the user is successfully authenticated, the RELAYCLIENT environment variable is effectively set for the SMTP session, and the TCPREMOTEINFO environment variable is set to the authenticated username, overriding any value that tcpserver may have set. The
value of TCPREMOTEINFO is reflected in a Received header.
Enhancements:
- bug: AUTH PLAIN 334 response not RFC compliant. Reported by Mark Crispin
- .
- change: Set TCPREMOTEINFO environment variable to authenticated username. (Previously only set locally to qmail-smtpd.)
Download (0.008MB)
Added: 2006-07-06 License: GPL (GNU General Public License) Price:
1228 downloads
karss 0.31
karss is an rss aggregator that displays multiple feeds in a single SuperKaramba theme, with entries sorted chronologically. more>>
karss is an rss aggregator that displays multiple feeds in a single SuperKaramba theme, with entries sorted chronologically. karss theme is based on multirss v1.2 by N7DR.
Differences include:
default dark background
larger font size (12 vs 10)
more entries at one time (25 vs 20)
reports "last updated" as time from last update
config option to use firefox instead of konqueror
rewritten and more managable innards
IMPORTANT INFO:
This theme depends on the PyXML package (for now). If you run it from command-line (superkaramba karss-03.skz), and get the following error:
> AttributeError: module object has no attribute DefaultHandler
Try installing the PyXML package. In kubuntu I believe this is called python-xml, so "sudo apt-get install python-xml". Please let me know if there are any other errors!
The first time you run karss, it will create a file feedlist.xml in a folder in your users superkaramba directory (usually ~/.superkaramba/karss) The format of the xml file should be fairly self-explanatory. Modify it accordingly to add or remove feeds.
Other features/improvements may be added later on.
Feedback/comments/screenshots appreciated!
<<lessDifferences include:
default dark background
larger font size (12 vs 10)
more entries at one time (25 vs 20)
reports "last updated" as time from last update
config option to use firefox instead of konqueror
rewritten and more managable innards
IMPORTANT INFO:
This theme depends on the PyXML package (for now). If you run it from command-line (superkaramba karss-03.skz), and get the following error:
> AttributeError: module object has no attribute DefaultHandler
Try installing the PyXML package. In kubuntu I believe this is called python-xml, so "sudo apt-get install python-xml". Please let me know if there are any other errors!
The first time you run karss, it will create a file feedlist.xml in a folder in your users superkaramba directory (usually ~/.superkaramba/karss) The format of the xml file should be fairly self-explanatory. Modify it accordingly to add or remove feeds.
Other features/improvements may be added later on.
Feedback/comments/screenshots appreciated!
Download (0.046MB)
Added: 2007-04-04 License: GPL (GNU General Public License) Price:
933 downloads
HTTP Server type 1.2.3
httptype is a program that returns the http host software of a website. more>>
httptype is a program that returns the http host software of a website. It is written in Perl.
httptype reads a list of http hosts and optionally the port number for each of these. It queries each host, displaying the type of HTTP server running on that host. It reads the http_proxy and no_proxy environment variables to determine whether to use a proxy or not.
httptype reads a list of http servers and, optionally, the port number for each of these. It then queries each of the hosts and displays the HTTP server software of the host.
Input may be read from a host file if specified using the --hosts switch:
httptype --hosts [hostfile]
If hostfile is omitted or `-, httptype reads from standard input. See Format of host file for more info.
A single host may be queried by passing its name on the command line:
httptype host [port]
If port is omitted, 80 is used.
If no host file is specified through the --hosts file and no host is specified on the command line, httptype will read the list from standard input. See Format of host file for more info.
httptype will read the http_proxy environment variable and try to determine if a proxy server is being used. This setting may be overridden using the --proxy switch:
httptype --proxy proxyhost[:proxyport]
If proxyport is omitted, 80 is used.
If the proxy server is `none, no proxy is used. This is typically used to prevent httptype from using the proxy server specified by http_proxy. The --noproxy switch can be used to achieve the same.
Additionally, you may use the no_proxy environment variable to specify a comma delimited list of hosts for which httptype should not use the proxy. If httptype comes across any of these hosts, it will make a direct connection to them.
Enhancements:
- made 1.3.8 stable and renamed to 1.2.3
<<lesshttptype reads a list of http hosts and optionally the port number for each of these. It queries each host, displaying the type of HTTP server running on that host. It reads the http_proxy and no_proxy environment variables to determine whether to use a proxy or not.
httptype reads a list of http servers and, optionally, the port number for each of these. It then queries each of the hosts and displays the HTTP server software of the host.
Input may be read from a host file if specified using the --hosts switch:
httptype --hosts [hostfile]
If hostfile is omitted or `-, httptype reads from standard input. See Format of host file for more info.
A single host may be queried by passing its name on the command line:
httptype host [port]
If port is omitted, 80 is used.
If no host file is specified through the --hosts file and no host is specified on the command line, httptype will read the list from standard input. See Format of host file for more info.
httptype will read the http_proxy environment variable and try to determine if a proxy server is being used. This setting may be overridden using the --proxy switch:
httptype --proxy proxyhost[:proxyport]
If proxyport is omitted, 80 is used.
If the proxy server is `none, no proxy is used. This is typically used to prevent httptype from using the proxy server specified by http_proxy. The --noproxy switch can be used to achieve the same.
Additionally, you may use the no_proxy environment variable to specify a comma delimited list of hosts for which httptype should not use the proxy. If httptype comes across any of these hosts, it will make a direct connection to them.
Enhancements:
- made 1.3.8 stable and renamed to 1.2.3
Download (0.014MB)
Added: 2006-07-11 License: GPL (GNU General Public License) Price:
1203 downloads
Bauk HTTP server 2.0.5
Bauk HTTP server project is a high-performance Web server. more>>
Bauk HTTP server project is a high-performance Web server. Bauks advanced architecture and unique design provide high performance and many original features, ie. ability to serve unlimited number of Virtual Hosts/simultaneous HTTP connections per single server process without performance loss.
Full installation requires only a single directory of UNIX file system used as a working directory for Bauk executable. Configuration process is simple and performed by adjustment of Bauk configuration script.
Main features:
- Full HTTP/1.1 and CGI/1.1 standard compliance
- HTTP authentication, Basic method, auth script per Virtual Host
- Unlimited number of Virtual Hosts without performance loss
- Virtual Host aliases
- Unlimited number of simultaneous HTTP connections per single Bauk process with no performance loss (Special Edition)
- Persistent (Keep-Alive) connections
- URL Path; define URL and path with type of access; ie. read, write, browse, execute, require HTTP authentication, etc.
- OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE methods of HTTP request defined by HTTP/1.1, configurable per URL Path
- Content negotiation by client language and charset
- Configurable MIME types
- Configurable HTTP headers by MIME type
- Configurable HTML error documents / CGI executables
- Directory browsing; view content of directories with HTML links
- Execution of CGI programs/scripts
- SUID/SGID for CGI execution
- Chroot for CGI execution; chroot CGI to Virtual Hosts home
- 3 security layers for CGI execution: by URL limit to X-only ie. CGI dir; for RX-URL imply X-only for X-able files; impose X-only by file extension ie. CGI executables wrongly placed and no X flag
- Quotas for CGI execution; number of simultaneous CGI processes, execution priority, max execution time (duration), max CPU time, memory, filesize
- Quotas of network traffic in/out per Virtual Host (I/O speed limit)
- Quotas of connections per Virtual Host
- Quotas of connections per client IP number
- Access restriction by IP address; forbid and allow-only
- Access restriction by valid HTTP referrer
- Configurable HTTP-log format and location for Virtual Hosts
- Configurable singleprocess or multiprocess architecture
- Chroot for Bauk server process
- Full configurability; virtually all Bauk features are configurable by simple configuration script adjustment
- Easy configuration by script language; built-in configuration script interpreter with preprocessor, file-inclusion, block and single-line comments, two data types, variables, arithmetic operations and built-in functions
- Easy administration
- Flexibility
VLAJKOS INVISIBLE LICENSE (VIL):
This sofware is protected by VIL and the license states:
Youre welcome to use this software. Remember the rightful author if youre using any parts/unique components of Bauk software.
Enhancements:
- This release includes various feature enhancements
- improved PHP, Perl, Gawk
- Tcl interpreter connectors
- additions to the documentation.
<<lessFull installation requires only a single directory of UNIX file system used as a working directory for Bauk executable. Configuration process is simple and performed by adjustment of Bauk configuration script.
Main features:
- Full HTTP/1.1 and CGI/1.1 standard compliance
- HTTP authentication, Basic method, auth script per Virtual Host
- Unlimited number of Virtual Hosts without performance loss
- Virtual Host aliases
- Unlimited number of simultaneous HTTP connections per single Bauk process with no performance loss (Special Edition)
- Persistent (Keep-Alive) connections
- URL Path; define URL and path with type of access; ie. read, write, browse, execute, require HTTP authentication, etc.
- OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE methods of HTTP request defined by HTTP/1.1, configurable per URL Path
- Content negotiation by client language and charset
- Configurable MIME types
- Configurable HTTP headers by MIME type
- Configurable HTML error documents / CGI executables
- Directory browsing; view content of directories with HTML links
- Execution of CGI programs/scripts
- SUID/SGID for CGI execution
- Chroot for CGI execution; chroot CGI to Virtual Hosts home
- 3 security layers for CGI execution: by URL limit to X-only ie. CGI dir; for RX-URL imply X-only for X-able files; impose X-only by file extension ie. CGI executables wrongly placed and no X flag
- Quotas for CGI execution; number of simultaneous CGI processes, execution priority, max execution time (duration), max CPU time, memory, filesize
- Quotas of network traffic in/out per Virtual Host (I/O speed limit)
- Quotas of connections per Virtual Host
- Quotas of connections per client IP number
- Access restriction by IP address; forbid and allow-only
- Access restriction by valid HTTP referrer
- Configurable HTTP-log format and location for Virtual Hosts
- Configurable singleprocess or multiprocess architecture
- Chroot for Bauk server process
- Full configurability; virtually all Bauk features are configurable by simple configuration script adjustment
- Easy configuration by script language; built-in configuration script interpreter with preprocessor, file-inclusion, block and single-line comments, two data types, variables, arithmetic operations and built-in functions
- Easy administration
- Flexibility
VLAJKOS INVISIBLE LICENSE (VIL):
This sofware is protected by VIL and the license states:
Youre welcome to use this software. Remember the rightful author if youre using any parts/unique components of Bauk software.
Enhancements:
- This release includes various feature enhancements
- improved PHP, Perl, Gawk
- Tcl interpreter connectors
- additions to the documentation.
Download (0.22MB)
Added: 2007-01-20 License: Other/Proprietary License Price:
1008 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 http dav 0.31 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