Free data provider or other service returned an e fail status access software for linux

Google::Adwords::Service is base class for the Service modules.

This module is not supposed to be used directly. Use the child Service modules.

METHODS

These accessors are available across all the child Service modules

new()

Creates a new Google::Adwords::Service object

Usage

my $service = Google::Adwords::CampaignService->new();

Parameters

NONE

Returns

A Google::Adwords::Service object

email()

Set/Get your Google Adwords account name (your email address). This value should be set before calling any other API methods

password()

Set/Get your Google Adwords account password. This value should be set before calling any other API methods

token()

Set/Get your Google Adwords developer token. This value should be set before calling any other API methods

clientEmail()

Use this if you have a MCC (My Client Center) account. Set/Get the actual client email which will be used for the API calls.

useragent()

Set this to an arbitrary string that identifies the customer sending the request. Default value is "Google::Adwords $VERSION"

use_sandbox()

If you do $obj->use_sandbox(1), then this module will use the sandbox for all API calls.

timeout()

Set the SOAP timeout value in seconds. Default value is 20.

debug()

Use $obj->debug(1) if you want to see the request/response XML

The following accessors are available after an API call is done. These give information about the response.

requestId()

Get the unique ID that identifies this request.

operations()

number of operations in the request

units()

number of quota units the request used

responseTime()

elapsed time between the web service receiving the request and sending the response

WebService::MusicBrainz is a Perl module that will act as a factory using static methods to return specific web service objects.

SYNOPSIS

use WebService::MusicBrainz;

my $artist_ws = WebService::MusicBrainz->new_artist();
my $track_ws = WebService::MusicBrainz->new_track();
my $release_ws = WebService::MusicBrainz->new_release();

METHODS

artist_new()

Return new instance of WebService::MusicBrainz::Artist object.

new_track

Return new instance of WebService::MusicBrainz::Track object.

new_release

Return new instance of WebService::MusicBrainz::Release object.

mpt-status is a query tool for accessing the running configuration and status of LSI SCSI HBAs. mpt-status is a heavily modified version of the original mpt-status-1.0 tool written by Matt Braithwaite.
It allows you to monitor the health and status of your RAID setup. Currently supported and tested HBAs are the LSI 1030 SCSI RAID storage controller and LSI SAS1064 SCSI RAID storage controller.
Since the tool uses the MPI (message passing interface), chances are high that the basic information regarding RAID status will be available for all LSI-based controllers.
Enhancements:
- This is the first release with proper 64-bit support and mostly clean interface querying.
- The mpt-status(8) man page has been added.
- Preliminary work has been done on integrating S.M.A.R.T information in the report output.
- This would allow one to monitor for failing hardware and preemptively replace it without business interruption.
- This information can be queried via the --newstyle/-n parameter.
- The new style parameter also provides you with the percentage status of the synchronization after a degradation.

The "Open Device Monitoring and Tracking Protocol", otherwise known as OpenDMTP, is a protocol and framework that allows bi-directional data communications between servers and devices (clients) over the Internet and similar networks.
OpenDMTP is a highly configurable and extensible protocol for communicating with mobile devices.
OpenDMTP is particularly geared towards Location-based information (LBS) such as GPS, as well as temperature and other data collected in remote-monitoring devices. OpenDMTP is small, and is especially suited for micro-devices such as PDAs, mobile phones, and custom OEM devices.
We saw a need for a communications protocol that allowed high-latency, low-bandwidth (HL/LB) devices to transmit location data to monitoring-systems. Because these devices often have limited network connectivity, the protocol needed to be small and efficient. Example devices include mobile phones, PDAs, OEM micro-devices (alarm systems, temperature monitors, etc.), and more.
There are many mobile GPS tracking devices on the market today with their own closed proprietary protocols. Searching the web for open protocols revealed only a few available for transferring data (including GPS information) between devices. However these solutions are generally designed for non-mobile applications and/or lack some of the low-bandwidth, configurable, and extensible features that mobile applications require.
Main features:
- Small Footprint: Mobile devices typically have limited resources on which to run client code (ie. memory, processor speed). An open protocol designed with this in mind should be optimized to allow efficient implementation and should easily support devices such as PDAs, mobile phones, GPS monitoring devices, and other OEM micro-devices.
- Network Efficient: Mobile devices typically have limited network connectivity, and in some cases data communication can be quite expensive (e.g. satellite). Because of this the protocol needs to be efficient in its dialog between the client and server. The communication needs to be optimized such that the necessary information can be conveyed with a minimum number of bytes in the least amount of time.
- Bi-directional: Some devices can support two-way communication (ie. GPRS, or other socket based connections), while others may only support one-way communication (ie. some satellite communication systems). With this in mind, a protocol should be designed to support both duplex (two-way) and simplex (one-way) communication.
- Transport Media: Differrent mobile applications will have their own unique way of communicating data back to the server. Some may use GPRS, or socket based communication, others may use satellite communication, while still others may use other forms of wireless communication, such as BlueTooth. The design of the protocol should be able to encompass all such transport media types, regardless of the type of transport in use.
- Flexible Data Encoding: Most types of transport media allow for the transmission of binary encoded data. However, there may be some forms of media for which an ASCII encoded data packet is much better suited. A protocol designed with this in mind should be able to support both types of data encoding.
- Configurable Messages: Due to the broad range of data types used in mobile applications, the protocol should be flexible enough to define standard messages, yet still allow custom messages within the framework.
- Extensible: Not every mobile application is the same. Some require special handling and may have various types of inputs and outputs. A protocol designed for mobile applications should insure that the framework can be easily extended to incapsulate the specific needs of the device.
- Industry Compatibility: Having an open protocol insures better compatibility between different client devices and service providers.
- Reference Implementation: Having a reference implementation that showcases the major features of the protocol provides an easy starting point on which developers can add their own features and platform specific implementation without having to worry about how data gets from the client to the server.
OpenDMTP was specifically designed to suit all these needs, especially "Small Footprint" and "Network Efficiency". The typical data plan for GPRS communication, for instance, is usually 1Mb per month. OpenDMTP was designed to optimize packet encoding to allow the collection of GPS information packets once every 3 minutes, 24 hours a day, 30 days a month, and still stay under the 1Mb data plan limit.
While XML is very extensible, it fails the "Small Footprint" and "Network Efficiency" requirements. Thus, it was discounted as a viable protocol solution. Many mobile devices do not have the resources necessary to be able to provide full XML parsing functionality. And an XML packet may need to be several hundred bytes in length just to send a few bytes of actual data. This alone would make the solution cost prohibitive for high-cost transport media such as satellite.
OpenDMTP also includes a full-featured commercial quality reference implementation to jump-start development.
Enhancements:
- NEW: Minor optimizations made to message logging.
- FIX: Log file now properly displays account/device on client connection.