perl interface cisco as5200 access router
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 10238
Imager::interface.pod 0.54
Imager::interface.pod decribes the C level virtual image interface. more>>
Imager::interface.pod decribes the C level virtual image interface.
The Imager virtual interface aims to allow image types to be created for special purposes, both to allow consistent access to images with different sample sizes, and organizations, but also to allow creation of synthesized or virtual images.
This is a C level interface rather than Perl.
<<lessThe Imager virtual interface aims to allow image types to be created for special purposes, both to allow consistent access to images with different sample sizes, and organizations, but also to allow creation of synthesized or virtual images.
This is a C level interface rather than Perl.
Download (0.83MB)
Added: 2006-10-27 License: Perl Artistic License Price:
1092 downloads
Cisco IP Accounting Fetcher 1.4.3
Cisco IP Accounting Fetcher is a set of Perl scripts that allows you to fetch IP accounting data from Cisco routers. more>>
Cisco IP Accounting Fetcher is a set of Perl scripts that allows you to fetch IP accounting data from Cisco routers. There is the only one config file - "getdata.conf for configuration.
Main features:
- fetch accounting data from the router
- generate the HTML statistics
<<lessMain features:
- fetch accounting data from the router
- generate the HTML statistics
Download (0.012MB)
Added: 2006-06-28 License: GPL (GNU General Public License) Price:
710 downloads
GnuPG::Interface 0.33
GnuPG::Interface is a Perl interface to GnuPG. more>>
GnuPG::Interface is a Perl interface to GnuPG.
SYNOPSIS
# A simple example
use IO::Handle;
use GnuPG::Interface;
# settting up the situation
my $gnupg = GnuPG::Interface->new();
$gnupg->options->hash_init( armor => 1,
homedir => /home/foobar );
# Note you can set the recipients even if you arent encrypting!
$gnupg->options->push_recipients( ftobin@cpan.org );
$gnupg->options->meta_interactive( 0 );
# how we create some handles to interact with GnuPG
my $input = IO::Handle->new();
my $output = IO::Handle->new();
my $handles = GnuPG::Handles->new( stdin => $input,
stdout => $output );
# Now well go about encrypting with the options already set
my @plaintext = ( foobar );
my $pid = $gnupg->encrypt( handles => $handles );
# Now we write to the input of GnuPG
print $input @plaintext;
close $input;
# now we read the output
my @ciphertext = ;
close $output;
waitpid $pid, 0;
GnuPG::Interface and its associated modules are designed to provide an object-oriented method for interacting with GnuPG, being able to perform functions such as but not limited to encrypting, signing, decryption, verification, and key-listing parsing.
How Data Member Accessor Methods are Created
Each module in the GnuPG::Interface bundle relies on Class::MethodMaker to generate the get/set methods used to set the objects data members. This is very important to realize. This means that any data member which is a list has special methods assigned to it for pushing, popping, and clearing the list.
Understanding Bidirectional Communication
It is also imperative to realize that this package uses interprocess communication methods similar to those used in IPC::Open3 and "Bidirectional Communication with Another Process" in perlipc, and that users of this package need to understand how to use this method because this package does not abstract these methods for the user greatly. This package is not designed to abstract this away entirely (partly for security purposes), but rather to simply help create proper, clean calls to GnuPG, and to implement key-listing parsing. Please see "Bidirectional Communication with Another Process" in perlipc to learn how to deal with these methods.
Using this package to do message processing generally invovlves creating a GnuPG::Interface object, creating a GnuPG::Handles object, setting some options in its options data member, and then calling a method which invokes GnuPG, such as clearsign. One then interacts with with the handles appropriately, as described in "Bidirectional Communication with Another Process" in perlipc.
<<lessSYNOPSIS
# A simple example
use IO::Handle;
use GnuPG::Interface;
# settting up the situation
my $gnupg = GnuPG::Interface->new();
$gnupg->options->hash_init( armor => 1,
homedir => /home/foobar );
# Note you can set the recipients even if you arent encrypting!
$gnupg->options->push_recipients( ftobin@cpan.org );
$gnupg->options->meta_interactive( 0 );
# how we create some handles to interact with GnuPG
my $input = IO::Handle->new();
my $output = IO::Handle->new();
my $handles = GnuPG::Handles->new( stdin => $input,
stdout => $output );
# Now well go about encrypting with the options already set
my @plaintext = ( foobar );
my $pid = $gnupg->encrypt( handles => $handles );
# Now we write to the input of GnuPG
print $input @plaintext;
close $input;
# now we read the output
my @ciphertext = ;
close $output;
waitpid $pid, 0;
GnuPG::Interface and its associated modules are designed to provide an object-oriented method for interacting with GnuPG, being able to perform functions such as but not limited to encrypting, signing, decryption, verification, and key-listing parsing.
How Data Member Accessor Methods are Created
Each module in the GnuPG::Interface bundle relies on Class::MethodMaker to generate the get/set methods used to set the objects data members. This is very important to realize. This means that any data member which is a list has special methods assigned to it for pushing, popping, and clearing the list.
Understanding Bidirectional Communication
It is also imperative to realize that this package uses interprocess communication methods similar to those used in IPC::Open3 and "Bidirectional Communication with Another Process" in perlipc, and that users of this package need to understand how to use this method because this package does not abstract these methods for the user greatly. This package is not designed to abstract this away entirely (partly for security purposes), but rather to simply help create proper, clean calls to GnuPG, and to implement key-listing parsing. Please see "Bidirectional Communication with Another Process" in perlipc to learn how to deal with these methods.
Using this package to do message processing generally invovlves creating a GnuPG::Interface object, creating a GnuPG::Handles object, setting some options in its options data member, and then calling a method which invokes GnuPG, such as clearsign. One then interacts with with the handles appropriately, as described in "Bidirectional Communication with Another Process" in perlipc.
Download (0.037MB)
Added: 2006-08-04 License: Perl Artistic License Price:
1176 downloads
RAS::AS5200 1.04
RAS::AS5200.pm is a Perl Interface to Cisco AS5200 Access Router. more>>
RAS::AS5200.pm is a Perl Interface to Cisco AS5200 Access Router.
SYNOPSIS
RAS::AS5200 is a PERL 5 module for interfacing with a Cisco AS5200 access router. Using this module, one can very easily construct programs to find a particular user in a bank of AS5200s, disconnect users, get usage statistics, or execute arbitrary commands on a AS5200.
<<lessSYNOPSIS
RAS::AS5200 is a PERL 5 module for interfacing with a Cisco AS5200 access router. Using this module, one can very easily construct programs to find a particular user in a bank of AS5200s, disconnect users, get usage statistics, or execute arbitrary commands on a AS5200.
Download (0.008MB)
Added: 2007-04-18 License: Perl Artistic License Price:
919 downloads
perlrpcgen 0.71
perlrpcgen is a Perl module that can generate Perl interfaces from ONC RPC interface definitions. more>>
perlrpcgen is a Perl module that can generate Perl interfaces from ONC RPC interface definitions.
SYNOPSIS
perlrpcgen [--makefile] [--all] [--client] [--server] [--data] [--constants] [--module module] [--typemap typemap] [--fork] [--perl perl] [--cc cc] [--rpclibs rpclibs] rpcfile.x
perlrpcgen builds a set of Perl extensions and a server shell from an ONC RPC interface definition. For an interface Foo, perlrpcgen creates modules Foo::Client, Foo::Data, and Foo::Constants. Foo::Client contains routines for creating a Foo client and making remote procedure calls via the client. Foo::Data contains routines for creating and manipulating the data structures defined in the Foo interface. Foo::Constants contains functions to retrieve the constants defined in the Foo interface.
OPTIONS
The option parsing uses Getopt::Long, so you can abbreviate option names.
--makefile
Generates a top-level Makefile which will build all the pieces. Include all the other options you want so theyll be propagated to the Makefile.
--all
Implies --client, --server, --data, and --constants. This is usually what you want.
--client
Generates Foo::Client module.
--server
Generates Foo/server/foo_svc.
--data
Generates Foo::Data module.
--constants
Generates Foo::Constants module.
--module module
Sets the basename of the modules. If not given, the name defaults to the basename of the interface file.
--typemap typemap
Uses the given typemap during stub generation. This option can be specified many times. perlrpcgen generates a typemap for the data structures in the interface, but you also need the main Perl typemap.
--fork
Munges the server shell code so that it forks for each request. You probably dont want to do this (its better to prefork several processes when you start the server and let them fight over accept() calls).
--perl perl
Sets the Perl binary against which extensions should be built. Defaults to the Perl you used to install perlrpcgen.
--cc cc
Sets the C compiler to use. Defaults to the compiler used when building Perl.
--rpclibs rpclibs
Sets the RPC libraries to link against. Defaults to -lnsl -lrpcsvc.
<<lessSYNOPSIS
perlrpcgen [--makefile] [--all] [--client] [--server] [--data] [--constants] [--module module] [--typemap typemap] [--fork] [--perl perl] [--cc cc] [--rpclibs rpclibs] rpcfile.x
perlrpcgen builds a set of Perl extensions and a server shell from an ONC RPC interface definition. For an interface Foo, perlrpcgen creates modules Foo::Client, Foo::Data, and Foo::Constants. Foo::Client contains routines for creating a Foo client and making remote procedure calls via the client. Foo::Data contains routines for creating and manipulating the data structures defined in the Foo interface. Foo::Constants contains functions to retrieve the constants defined in the Foo interface.
OPTIONS
The option parsing uses Getopt::Long, so you can abbreviate option names.
--makefile
Generates a top-level Makefile which will build all the pieces. Include all the other options you want so theyll be propagated to the Makefile.
--all
Implies --client, --server, --data, and --constants. This is usually what you want.
--client
Generates Foo::Client module.
--server
Generates Foo/server/foo_svc.
--data
Generates Foo::Data module.
--constants
Generates Foo::Constants module.
--module module
Sets the basename of the modules. If not given, the name defaults to the basename of the interface file.
--typemap typemap
Uses the given typemap during stub generation. This option can be specified many times. perlrpcgen generates a typemap for the data structures in the interface, but you also need the main Perl typemap.
--fork
Munges the server shell code so that it forks for each request. You probably dont want to do this (its better to prefork several processes when you start the server and let them fight over accept() calls).
--perl perl
Sets the Perl binary against which extensions should be built. Defaults to the Perl you used to install perlrpcgen.
--cc cc
Sets the C compiler to use. Defaults to the compiler used when building Perl.
--rpclibs rpclibs
Sets the RPC libraries to link against. Defaults to -lnsl -lrpcsvc.
Download (0.037MB)
Added: 2007-05-31 License: Perl Artistic License Price:
876 downloads
Perl OS 4
Perl OS is a program written in Perl/Tk, designed to look like a simple operating system. more>>
Perl OS is a program written in the Perl programming language combined with the Perl module Tk.
Perl OS was created to make an easy interface to run Perl/Tk programs. It was also created to be an easy working environment complete with a text editor, paint program, and more.
The program comes with several programs, along with a utility to add many more which can be found on the Internet.
From the outside, Perl OS looks like a simple operating system. But inside, it is a powerful system for working with Perl and Tk.
For more details please visit the Perl OS home page:
http://perlos.sourceforge.net/
<<lessPerl OS was created to make an easy interface to run Perl/Tk programs. It was also created to be an easy working environment complete with a text editor, paint program, and more.
The program comes with several programs, along with a utility to add many more which can be found on the Internet.
From the outside, Perl OS looks like a simple operating system. But inside, it is a powerful system for working with Perl and Tk.
For more details please visit the Perl OS home page:
http://perlos.sourceforge.net/
Download (0.14MB)
Added: 2007-08-04 License: GPL v3 Price:
812 downloads
Net::AudioScrobbler 0.01
Net::AudioScrobbler is a Perl module that provides an interface to AudioScrobbler. more>>
Net::AudioScrobbler is a Perl module that provides an interface to AudioScrobbler.
Installation:
To install this module type the following:
perl Makefile.PL
make
make test
make install
<<lessInstallation:
To install this module type the following:
perl Makefile.PL
make
make test
make install
Download (0.003MB)
Added: 2007-03-23 License: Perl Artistic License Price:
945 downloads
WebService::Upcoming 0.05
WebService::Upcoming is a Perl interface to the Upcoming API. more>>
WebService::Upcoming is a Perl interface to the Upcoming API.
SYNOPSIS
use WebService::Upcoming;
my $upco = new WebService::Upcoming("*** UPCOMING API KEY HERE ***");
my $objc = $upco->call("event.search",
{
"search_text" => "music"
});
die("ERROR: ".$upco->err_text()."n") if (!defined($objc));
foreach (@{$objc})
{
print("EVENT: ".$_->name()." on ".$_->start_date()."n");
}
A simple interface for using the Upcoming API.
WebService::Upcoming is a subclass of LWP::UserAgent, so all of the various proxy, request limits, caching, and other features are available.
<<lessSYNOPSIS
use WebService::Upcoming;
my $upco = new WebService::Upcoming("*** UPCOMING API KEY HERE ***");
my $objc = $upco->call("event.search",
{
"search_text" => "music"
});
die("ERROR: ".$upco->err_text()."n") if (!defined($objc));
foreach (@{$objc})
{
print("EVENT: ".$_->name()." on ".$_->start_date()."n");
}
A simple interface for using the Upcoming API.
WebService::Upcoming is a subclass of LWP::UserAgent, so all of the various proxy, request limits, caching, and other features are available.
Download (0.006MB)
Added: 2007-04-02 License: Perl Artistic License Price:
935 downloads
WebService::ISBNDB 0.31
WebService::ISBNDB Perl module provides an object-oriented interface to the data API at http://isbndb.com. more>>
WebService::ISBNDB Perl module provides an object-oriented interface to the data API at http://isbndb.com. Books, authors, publishers, categories, and subjects are all represented in separate classes. The module uses the REST interface to communicate with isbndb.com.
<<less Download (0.040MB)
Added: 2006-10-14 License: Artistic License Price:
1106 downloads
ObjStore::Internals 1.59
ObjStore::Internals is a Perl module with a few notes on the implementation. more>>
ObjStore::Internals is a Perl module with a few notes on the implementation.
SYNOPSIS
You dont have to understand anything about the technical implementation. Just know that:
ObjectStore is outrageously powerful; sophisticated; and even over-engineered.
The perl interface is optimized to be fun and easy. Since ObjectStore is also blindingly fast, you can happily leave relational databases to collect dust on the bookshelf where they belong.
So basically, you dont have to understand anything to a greater depth. Its not necessary. Youve arrived. You will be successful. However, more detail follows. If you like to turn things inside-out, read on!
Perl & C++ APIs: Whats The Difference?
Most stuff should be roughly the same. The few exceptions have generally arisen because there was a perl way to make the interface more programmer friendly.
Transactions are perlified.
Some static methods sit directly under ObjStore:: instead of under their own classes. (Easier to import.)
Databases are always blessed according to your pleasure.
lookup, open, is_open, and lock_timeout are augmented with multi-color, pop-tart style interfaces.
Why not just store perl data with the usual perl structures?
CHANGE CONTROL
As perl evolves, new data layouts are introduced. These changes must not cause database compatibility problems.
BINARY COMPATIBILITY
Perl doesnt have to worry about binary compatibility between platforms. Databases do. In addition, databases impose a number of restrictions on persistent data layout that would be onerous and sub-optimal if adopted by perl.
MEMORY USAGE
Perl often trades memory for speed. This is the wrong trade for a database. Memory usage is much more of a concern when data sets can be as large or larger than ten million megabytes. A few percent difference in compactness can be quite noticable.
<<lessSYNOPSIS
You dont have to understand anything about the technical implementation. Just know that:
ObjectStore is outrageously powerful; sophisticated; and even over-engineered.
The perl interface is optimized to be fun and easy. Since ObjectStore is also blindingly fast, you can happily leave relational databases to collect dust on the bookshelf where they belong.
So basically, you dont have to understand anything to a greater depth. Its not necessary. Youve arrived. You will be successful. However, more detail follows. If you like to turn things inside-out, read on!
Perl & C++ APIs: Whats The Difference?
Most stuff should be roughly the same. The few exceptions have generally arisen because there was a perl way to make the interface more programmer friendly.
Transactions are perlified.
Some static methods sit directly under ObjStore:: instead of under their own classes. (Easier to import.)
Databases are always blessed according to your pleasure.
lookup, open, is_open, and lock_timeout are augmented with multi-color, pop-tart style interfaces.
Why not just store perl data with the usual perl structures?
CHANGE CONTROL
As perl evolves, new data layouts are introduced. These changes must not cause database compatibility problems.
BINARY COMPATIBILITY
Perl doesnt have to worry about binary compatibility between platforms. Databases do. In addition, databases impose a number of restrictions on persistent data layout that would be onerous and sub-optimal if adopted by perl.
MEMORY USAGE
Perl often trades memory for speed. This is the wrong trade for a database. Memory usage is much more of a concern when data sets can be as large or larger than ten million megabytes. A few percent difference in compactness can be quite noticable.
Download (0.16MB)
Added: 2007-02-09 License: Perl Artistic License Price:
989 downloads
WebService::Kizasi 0.1.0
WebService::Kizasi is a Perl Interface for the Kizasi Web Services. more>>
WebService::Kizasi is a Perl Interface for the Kizasi Web Services.
SYNOPSIS
use WebService::Kizasi;
use Encode qw(_utf8_off);
my $kizapi = WebService::Kizasi->new();
my @result;
$result[0] = $kizapi->c10e_word_1d(CPAN);
$result[1] = $kizapi->c10e_word_1w(CPAN);
$result[2] = $kizapi->c10e_word_1m(CPAN);
$result[3] = $kizapi->keyword_in_context(CPAN);
$result[4] = $kizapi->ranking_1d;
$result[5] = $kizapi->ranking_1w;
$result[6] = $kizapi->ranking_1m;
for my $result (@result) {
my $utf8off = $result->items->[0]->title;
_utf8_off ($utf8off);
print $utf8off,"n";
print $result->items->[0]->pubDate,"n";
print $result->items->[0]->link,"n";
print $result->items->[0]->guid,"n";
$utf8off = $result->items->[0]->description;
_utf8_off($utf8off);
print $utf8off,"n";
}
Kizasi.jp is the sight which discovers the "sign of change" (Kizasi) from blogs, and the WebService::Kizasi is a Perl interface to the Kizasi WebService API (Kizapi). For details, see http://blog.kizasi.jp/kizasi/66.
<<lessSYNOPSIS
use WebService::Kizasi;
use Encode qw(_utf8_off);
my $kizapi = WebService::Kizasi->new();
my @result;
$result[0] = $kizapi->c10e_word_1d(CPAN);
$result[1] = $kizapi->c10e_word_1w(CPAN);
$result[2] = $kizapi->c10e_word_1m(CPAN);
$result[3] = $kizapi->keyword_in_context(CPAN);
$result[4] = $kizapi->ranking_1d;
$result[5] = $kizapi->ranking_1w;
$result[6] = $kizapi->ranking_1m;
for my $result (@result) {
my $utf8off = $result->items->[0]->title;
_utf8_off ($utf8off);
print $utf8off,"n";
print $result->items->[0]->pubDate,"n";
print $result->items->[0]->link,"n";
print $result->items->[0]->guid,"n";
$utf8off = $result->items->[0]->description;
_utf8_off($utf8off);
print $utf8off,"n";
}
Kizasi.jp is the sight which discovers the "sign of change" (Kizasi) from blogs, and the WebService::Kizasi is a Perl interface to the Kizasi WebService API (Kizapi). For details, see http://blog.kizasi.jp/kizasi/66.
Download (0.012MB)
Added: 2007-02-08 License: Perl Artistic License Price:
988 downloads
WebService::Basecamp 0.1.3
WebService::Basecamp is a Perl interface to the Basecamp API webservice. more>>
WebService::Basecamp is a Perl interface to the Basecamp API webservice.
SYNOPSIS
use WebService::Basecamp;
my $bc = WebService::Basecamp->new( url => http://mysite.clientsection.com,
user => username,
pass => password );
my $test = $bc->ping || die $bc->error();
my $projects = $bc->projects; # a list of all projects
Basecamp is a web based project collaboration tool that makes it simple to communicate and collaborate on projects. Basecamp is built on the Ruby on Rails platform but provides a webservice API to many of the application functions. WebService::Basecamp is a Perl interface to the Basecamp web service API.
For more information on Basecamp, visit the Basecamp website. http://www.basecamphq.com.
This module does much of the heavy lifting for you when accessing the Basecamp API. Once initialising a WebService::Basecamp object you can access the API function via method calls. The module takes care of the creation and parsing of the XML (using XML::Simple) that relays the data across the web service, however there is an option to access the XML directly (see new()).
The documentation for this module is based on the Basecamp API docs available at http://www.basecamphq.com/api. It is recommended you read the official docs to become familiar with the data reference.
<<lessSYNOPSIS
use WebService::Basecamp;
my $bc = WebService::Basecamp->new( url => http://mysite.clientsection.com,
user => username,
pass => password );
my $test = $bc->ping || die $bc->error();
my $projects = $bc->projects; # a list of all projects
Basecamp is a web based project collaboration tool that makes it simple to communicate and collaborate on projects. Basecamp is built on the Ruby on Rails platform but provides a webservice API to many of the application functions. WebService::Basecamp is a Perl interface to the Basecamp web service API.
For more information on Basecamp, visit the Basecamp website. http://www.basecamphq.com.
This module does much of the heavy lifting for you when accessing the Basecamp API. Once initialising a WebService::Basecamp object you can access the API function via method calls. The module takes care of the creation and parsing of the XML (using XML::Simple) that relays the data across the web service, however there is an option to access the XML directly (see new()).
The documentation for this module is based on the Basecamp API docs available at http://www.basecamphq.com/api. It is recommended you read the official docs to become familiar with the data reference.
Download (0.023MB)
Added: 2007-01-11 License: Perl Artistic License Price:
1017 downloads
Bio::Factory::SequenceFactoryI 1.4
Bio::Factory::SequenceFactoryI is a Perl interface that allows for generic building of sequences in factories. more>>
Bio::Factory::SequenceFactoryI is a Perl interface that allows for generic building of sequences in factories which create sequences (like SeqIO).
SYNOPSIS
# do not use this object directly it is an interface # get a Bio::Factory::SequenceFactoryI object like
use Bio::Seq::SeqFactory;
my $seqbuilder = new Bio::Seq::SeqFactory(type => Bio::PrimarySeq);
my $seq = $seqbuilder->create(-seq => ACTGAT,
-display_id => exampleseq);
print "seq is a ", ref($seq), "n";
A generic way to build Sequence objects via a pluggable factory. This reduces the amount of code that looks like
if( $type eq Bio::PrimarySeq ) { ... }
elsif( $type eq Bio::Seq::RichSeq ) { ... }
<<lessSYNOPSIS
# do not use this object directly it is an interface # get a Bio::Factory::SequenceFactoryI object like
use Bio::Seq::SeqFactory;
my $seqbuilder = new Bio::Seq::SeqFactory(type => Bio::PrimarySeq);
my $seq = $seqbuilder->create(-seq => ACTGAT,
-display_id => exampleseq);
print "seq is a ", ref($seq), "n";
A generic way to build Sequence objects via a pluggable factory. This reduces the amount of code that looks like
if( $type eq Bio::PrimarySeq ) { ... }
elsif( $type eq Bio::Seq::RichSeq ) { ... }
Download (4.7MB)
Added: 2006-09-02 License: Perl Artistic License Price:
1147 downloads
Mozilla::PromptService 0.03
Mozilla::PromptService is a Perl interface to the Mozilla nsIPromptService. more>>
Mozilla::PromptService is a Perl interface to the Mozilla nsIPromptService.
SYNOPSIS
use Mozilla::PromptService;
Mozilla::PromptService::Register({
Alert => sub {
my ($parent, $title, $dialog_text) = @_;
# do something smart on alert ...
},
# Prompt callback should return result
Prompt => sub { return "Prompt Result" },
DEFAULT => sub {
my ($name, $parent, $title, $dialog_text) = @_;
# some other confirmation is needed
}
}
Mozilla::PromptService uses Mozilla nsIPromptService to allow perl callbacks on prompt events.
For a much more detailed information on nsIPromptService see documentation on mozilla.org
<<lessSYNOPSIS
use Mozilla::PromptService;
Mozilla::PromptService::Register({
Alert => sub {
my ($parent, $title, $dialog_text) = @_;
# do something smart on alert ...
},
# Prompt callback should return result
Prompt => sub { return "Prompt Result" },
DEFAULT => sub {
my ($name, $parent, $title, $dialog_text) = @_;
# some other confirmation is needed
}
}
Mozilla::PromptService uses Mozilla nsIPromptService to allow perl callbacks on prompt events.
For a much more detailed information on nsIPromptService see documentation on mozilla.org
Download (0.034MB)
Added: 2007-03-22 License: Perl Artistic License Price:
946 downloads
Audio::Scrobbler 0.01
Audio::Scrobbler is a Perl interface to audioscrobbler.com/last.fm. more>>
Audio::Scrobbler is a Perl interface to audioscrobbler.com/last.fm.
SYNOPSIS
use Audio::Scrobbler;
$scrob = new Audio::Scrobbler(cfg => { ... });
$scrob->handshake();
$scrob->submit(artist => "foo", album => "hello", track => "world",
length => 180);
The Audio::Scrobbler module provides a Perl interface to the track submission API of Last.fms AudioScrobbler - http://www.audioscrobbler.com/. So far, only track submissions are handled; the future plans include access to the various statistics.
<<lessSYNOPSIS
use Audio::Scrobbler;
$scrob = new Audio::Scrobbler(cfg => { ... });
$scrob->handshake();
$scrob->submit(artist => "foo", album => "hello", track => "world",
length => 180);
The Audio::Scrobbler module provides a Perl interface to the track submission API of Last.fms AudioScrobbler - http://www.audioscrobbler.com/. So far, only track submissions are handled; the future plans include access to the various statistics.
Download (0.07MB)
Added: 2006-06-30 License: GPL (GNU General Public License) Price:
1211 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 perl interface cisco as5200 access router 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