Introduction

The Photobucket API allows you to create an interface to “talk” to the Photobucket web site. This means that users do not have to leave your site to perform certain actions on the Photobucket site, such as:

• Uploading images.
• Uploading video
• Getting all recent media (videos and images) for:
• A specific user.
• All users.
• Group albums.
• Searching media matching a specific term or terms in:
• One user’s account.
• All user accounts.
• Group albums.
• Getting all details associated with one piece of media, such as:
• Link URLs.
• Thumbnail URL.
• Updating titles, descriptions, and tags.

Using the Documentation

Chapter 1. Overview
What is YQL?
The YQL Web Service enables applications to query, filter, and combine data from different sources across the Internet. YQL statements have a SQL-like syntax, familiar to any developer with database experience. The following YQL statement, for example, retrieves a list of cat photos from Flickr:

SELECT * FROM flickr.photos.search WHERE text=”cat”

To access the YQL Web Service, a Web application can call HTTP GET, passing the YQL statement as a URL parameter, for example:

http://query.yahooapis.com/v1/public/yql?q=SELECT * FROM flickr.photos.search WHERE text=”Cat”

When it processes a query, the YQL Web Service accesses a datasource on the Internet, transforms the data, and returns the results in either XML or JSON format. YQL can access several types of datasources, including Yahoo! Web Services, other Web services, and Web content in formats such as HTML, XML,
RSS, and Atom.

Introduction

The PPC (Performance Prediction Component) is a tool to study the behavior of some selected MPI kernels in the Grid. It is based on a set of models that characterize the behavior of the kernels when they are executed in the Grid. These models were obtained from exhaustive executions on different Grid scenarios. From these measurements a methodology to obtain correlations between performance and monitoring information is applied to obtain easy to use functions to characterize the execution of the kernel. Even though the tool is limited to a set of specific kernels, it can be easily extended to others. Note that some of the kernels are general purpose. i.e. communications, that could be useful for any user.

Introduction
This guide explains how to write mobile applications for the Yahoo! BlueprintTM Platform. Specifically, it documents the Blueprint markup language and provides instructions for developing, testing, and publishing mobile Internet services.

Understanding the Yahoo! Blueprint Platform

• Using Blueprint, third-party developers can provide custom content and services in a variety of ways. Applications can be Yahoo! Go Mobile Widgets, browser-based Mobile Sites, or stand-alone Mobile Apps:
• Mobile Widgets run under Yahoo! Go. Users can subscribe to published Widgets by selecting them from the Widget Gallery and add Widgets to the Yahoo! Go carousel for faster access.
• Mobile Sites are accessible from any standard Web browser. Once published, they can be found using the search facility on Yahoo!’s mobile homepage.
• Mobile Apps rely on a stand-alone version of the Blueprint runtime installed on the user’s phone.

They are accessed independently of both Web browsers and Yahoo! Go. The deployment sections in this guide focus on Widgets. For information about publishing Mobile Sites and Mobile Apps, see the supplementary documents available from Yahoo!’s Mobile Developer site.

Introduction
Processes and threads: in underlying OS and in Windows
Before going into the depths of debugging in Wine, here’s a small overview of process and thread handling in Wine. It has to be clear that there are two different beasts: processes/threads from the Unix point of view and processes/threads from a Windows point of view.

Each Windows’ thread is implemented as a Unix thread, meaning that all threads of a same Windows’ process share the same (unix) address space.

In the following:

• W-process means a process in Windows’ terminology
• U-process means a process in Unix’ terminology
• W-thread means a thread in Windows’ terminology

A W-process is made of one or several W-threads. Each W-thread is mapped to one and only one U-process. All U-processes of a same W-process share the same address space.

This book is organized as follows:

• Chapter 1, Introducing ObjectStore, on page 1, describes what ObjectStore does, shows the application architecture, and defines some important terms.
• Chapter 2, Example of Using ObjectStore, on page 13, describes the components your application must include to use ObjectStore.
• Chapter 3, Using Sessions to Manage Threads, on page 19, discusses how to initialize threads to use ObjectStore and how to use threads with ObjectStore sessions.
• Chapter 4, Managing Databases, on page 49, provides instructions for creating, opening, closing, garbage collecting, and upgrading databases.
• Chapter 5, Working with Transactions, on page 85, describes how to start and end transactions.
• Chapter 6, Storing, Retrieving, and Updating Objects, on page 99, discusses the steps for storing, retrieving, and updating data.
• Chapter 7, Working with Collections, on page 157, provides information about how to create collections of objects and run queries over the collections.