Free amazon.com software for linux

Net::Amazon is a framework for accessing amazon.com via REST.

SYNOPSIS

use Net::Amazon;

my $ua = Net::Amazon->new(token => YOUR_AMZN_TOKEN);

# Get a request object
my $response = $ua->search(asin => 0201360683);

if($response->is_success()) {
print $response->as_string(), "n";
} else {
print "Error: ", $response->message(), "n";
}

ABSTRACT

Net::Amazon provides an object-oriented interface to amazon.coms
REST interface. This way its possible to create applications
using Amazons vast amount of data via a functional interface, without
having to worry about the underlying communication mechanism.

Net::Amazon works very much like LWP: First you define a useragent like

my $ua = Net::Amazon->new(
token => YOUR_AMZN_TOKEN,
max_pages => 3,
);

which you pass your personal amazon developers token (can be obtained from http://amazon.com/soap) and (optionally) the maximum number of result pages the agent is going to request from Amazon in case all results dont fit on a single page (typically holding 20 items). Note that each new page requires a minimum delay of 1 second to comply with Amazons one-query-per-second policy.

According to the different search methods on Amazon, theres a bunch of different request types in Net::Amazon. The user agents convenience method search() triggers different request objects, depending on which parameters you pass to it:

$ua->search(asin => "0201360683")
The asin parameter has Net::Amazon search for an item with the specified ASIN. If the specified value is an arrayref instead of a single scalar, like in
$ua->search(asin => ["0201360683", "0596005083"])
then a search for multiple ASINs is performed, returning a list of results.
$ua->search(actor => "Adam Sandler")
The actor parameter has the user agent search for items created by the specified actor. Can return many results.
$ua->search(artist => "Rolling Stones")
The artist parameter has the user agent search for items created by the specified artist. Can return many results.
$ua->search(author => "Robert Jordan")
The author parameter has the user agent search for items created by the specified author. Can return many results.
$ua->search(browsenode=>"4025", mode=>"books" [, keywords=>"perl"])
Returns a list of items by category ID (node). For example node "4025" is the CGI books category. You can add a keywords parameter to filter the results by that keyword.
$ua->search(exchange => Y04Y3424291Y2398445)
Returns an item offered by a third-party seller. The item is referenced by the so-called exchange ID.
$ua->search(keyword => "perl xml", mode => "books")
Search by keyword, mandatory parameters keyword and mode. Can return many results.
$ua->search(wishlist => "1XL5DWOUFMFVJ")
Search for all items in a specified wishlist. Can return many results.
$ua->search(upc => "075596278324", mode => "music")
Music search by UPC (product barcode), mandatory parameter upc. mode has to be set to music. Returns at most one result.
$ua->search(isbn => "0439784549")
Book search by ISBN (International Standard Book Number), mandatory parameter isbn. Returns at most one result. When searching non-US locales use the 13-digit ISBN.
$ua->search(similar => "0201360683")
Search for all items similar to the one represented by the ASIN provided. Can return many results.
$ua->search(power => "subject: perl and author: schwartz", mode => "books")
Initiate a power search for all books matching the power query. Can return many results. See Net::Amazon::Request::Power for details.
$ua->search(manufacturer => "Disney")
Initiate a search for all items made by a given manufacturrer. Can return many results. See Net::Amazon::Request::Manufacturer for details.
$ua->search(musiclabel => "Arista")
Initiate a search for all items made by a given music label. Can return many results. See Net::Amazon::Request::MusicLabel for details.
$ua->search(publisher => "oreilly")
Initiate a search for all items made by a given publisher. Can return many results. See Net::Amazon::Request::Publisher for details.
$ua->search(blended => "Perl")
Initiate a search for items in all categories.
$ua->search(seller => "A2GXAGU54VOP7")
Start a search on items sold by a specific third-party seller, referenced by its ID (not seller name).
$ua->search(textstream => "Blah blah Rolling Stones blah blah")
Find items related to keywords within a text stream.
The user agents search method returns a response object, which can be checked for success or failure:
if($resp->is_success()) {
print $resp->as_string();
} else {
print "Error: ", $resp->message(), "n";
}

In case the request for an item search succeeds, the response contains one or more Amazon properties, as it calls the products found. All matches can be retrieved from the Response object using its properties() method.

In case the request fails, the response contains one or more error messages. The response objects message() method will return it (or them) as a single string, while messages() (notice the plural) will return a reference to an array of message strings.

Response objects always have the methods is_success(), is_error(), message(), total_results(), as_string() and properties() available.
total_results() returns the total number of results the search yielded. properties() returns one or more Net::Amazon::Property objects of type Net::Amazon::Property (or one of its subclasses like Net::Amazon::Property::Book, Net::Amazon::Property::Music or Net::Amazon::Property::DVD), each of which features accessors named after the attributes of the product found in Amazons database:

for ($resp->properties) {
print $_->Asin(), " ",
$_->OurPrice(), "n";
}

In scalar context, properties() just returns the first Net::Amazon::Property object found. Commonly available accessors to Net::Amazon::Property objects are OurPrice(), ImageUrlLarge(), ImageUrlMedium(), ImageUrlSmall(), ReleaseDate(), Catalog(), Asin(), url(), Manufacturer(), UsedPrice(), ListPrice(), ProductName(), Availability(), SalesRank(), CollectiblePrice(), CollectibleCount(), NumberOfOfferings(), UsedCount(), ThirdPartyNewPrice(), ThirdPartyNewCount(), similar_asins(). For details, check Net::Amazon::Property.

Also, the specialized classes Net::Amazon::Property::Book and Net::Amazon::Property::Music feature convenience methods like authors() (returning the list of authors of a book) or album() for CDs, returning the album title.

Customer reviews: Every property features a review_set() method which returns a Net::Amazon::Attribute::ReviewSet object, which in turn offers a list of Net::Amazon::Attribute::Review objects. Check the respective man pages for details on whats available.

Amazon Mini Shop allows you to search Amazon.com, .co.uk, .de, .fr, .ca or .co.jp from the sidebar.
Main features:
- Search all Amazon sites from the sidebar
- Images with results (mouse over to enlarge)
- Add search as a RSS live bookmark

SQL::Amazon::Request::Help is an Interface to retrieve Help content.

SYNOPSIS

$dbh = DBI->connect(dbi:Amazon:, $amznid, undef,
{ amzn_mode => books,
amzn_locale => us,
amzn_max_pages => 3
})
or die "Cannot connect: " . $DBI::errstr;
#
# search for some Perl DBI books
#
$sth = $dbh->prepare("
SELECT ASIN,
Title,
Publisher,
PublicationDate,
Author,
SmallImageURL,
URL,
SalesRank,
ListPriceAmt,
AverageRating
FROM Books
WHERE MATCHES ALL(Perl, DBI) AND
PublicationDate >= 2000-01-01
ORDER BY SalesRank DESC,
ListPriceAmt ASC,
AverageRating DESC");

$sth->execute or die Cannot execute: . $sth->errstr;

print join(, , @$row), "n"
while $row = $sth->fetchrow_arrayref;

$dbh->disconnect;

DBD::Amazon provides a DBI and SQL syntax abstraction for the Amazon(R) E-Commerce Services 4.0 API *aka* ECS. < http://www.amazon.com/gp/ >. Using the REST interface, and a limited SQL dialect, it provides a DBI-friendly interface to ECS.

Be advised that this is ALPHA release software and subject to change at the whim of the author(s).

SQL::Statement::Embed can embed a SQL engine in a DBD or module.

SQL::Statement is designed to be easy to embed in other modules and to be especially easy to embed in DBI drivers. It provides a SQL Engine and the other module needs to then provide a data source and a storage mechanism. For example, the DBD::CSV module uses SQL::Statement as an embedded SQL engine by implementing a file-based data source and by using DBI as the user interface. Similarly DBD::Amazon uses SQL::Statement as its SQL engine, provides its own extensions to the supported SQL syntax, and uses on-the-fly searches of Amazon.com as its data source.

SQL::Statement is the basis for eight existing DBDs (DBI database drivers). If you have a new data source, you too can create a DBD without having to reinvent the SQL wheel. Its fun, its easy, become a DBD author today!

SQL::Statement can be also be embedded without DBI. Well explore that first since developing a DBD uses most of the same methods and techniques.

The role of SQL::Statement subclasses

SQL::Statement provides a SQL parsing and execution engine. It does not provide a data source or storage mechanism other than in-memory tables. The DBD::File module is a subclass of SQL::Statement that provides access to file-based storage mechanisms. Its quite possible to use things other than files as data souces, in which case we wouldnt use DBD::File, instead wed replace DBD::Files methods with our own. In the examples below, well use DBD::File, replacing only a few methods.

SQL::Statement provides SQL parsing and evaluation and DBD::File provides file-based storage. The only thing missing is a data source - what we actually want to store and query. As an example suppose we are going to create a subclass called Foo that will provide as a data source a simple file similar to a passwd file - one record per line, fields separated by colons, with only three fields "username, uid, gid".

Consider what needs to happen to perform a SELECT query on our Foo data:

* recieve a SQL string
* parse the SQL string into a request structure
* open the table(s) specified in the request
* define column names and postions for the table
* read rows from the table
* convert the rows from colon-separated format into perl arrays
* match the columns and rows against the requested selection criteria
* return requested rows and columns to the user

To perform operations like INSERT and DELETE, we also need to:

* convert rows from perl arrays into colon-separated format
* write rows
* delete rows

SQL::Statement takes care of all of the SQL parsing and evaluation. DBD::File takes care of file opening, reading, writing, and deleting. So the only things Foo is really responsible for are:

* define column names and postions for the table
* convert rows from colon-separated format into perl arrays
* convert rows from perl arrays into colon-separated format

In SQL::Statement subclasses these responsibilities are assigned to two objects, a ::Statement object is responsible for opening the table, defining the column names and positions, and for creating new ::Table objects. A ::Table object is responsible for reading, converting, writing, and deleting data.

Koha is a library and collection management system. It is designed to manage physical collections of items (books, CDs, videos, reference, etc.). Koha provides cataloguing, searching, member/patron management, an acqusitions system, and circulation (issues, returns, and reserves).
Enhancements:
- Many bugs in Acquisitions have been fixed, and online help has been added.
- Serial items can now be created on the fly.
- There is a new option to include book covers, description, and reviews for items from Amazon.com.

Myghty is a Python based web and templating framework originally based on HTML::Mason, the enterprise-level framework used by Amazon.com, del.icio.us and Salon.com, among many others.
Myghty fully implements Masons templating language, component-based architecture, and caching system, and goes beyond, adding new paradigms such as Module Components, full Python whitespace syntax, threading support, WSGI support, session support, and much more.
Main features:
- Session object support.
- Direct connectors for mod_python, CGI, WSGI, Python Paste, SimpleHTTPServer. As the Interpreter object is a lightweight object with no external dependencies whatsoever, any Python application or application server can invoke any series of Myghty components with just one line of code.
- A super-configurable ruleset driven URI resolution architecture allowing many options for resolving URIs both externally and within templates. Allows any combination of resolution directly to templates, Module Components, or any plain Python function or object instance. Special rules exist to route non-existent URIs to specific components, to cache the results of URI resolution for higher performance, and to execute conditionally based on contextual information.
- Cache API and implementation, can cache component output and any other data structure in memory or in pickled files. Includes a "busy lock" feature that allows a slow re-generation method to execute while the old data continues to be returned to other threads and processes. New cache implementations can be added fairly easily.
- Flexible global namespaces allow components to have any number of custom "global" variables.
- Special code blocks allow the construction of code that is local to the current request, or local to the current thread. A ThreadLocal object is supplied as well for safe management of thread-sensitive resources such as databases.
- Fine grained control of buffering - the buffering of textual output as it is delivered to the client can controlled at the application, page, or component level.
- Custom filtering functions can be defined for the output any component, within the source of the component via the