This document discusses IPv6 addressing and formatting recommendations. It provides examples of valid IPv6 addresses and comparisons. RFC5952 rules for representing IPv6 addresses are presented, with notes on incompatible rules. The discussion includes using the PEAR::Net_IPv6 PHP library for IPv6 validation and address compression, along with submitting a patch to make the library compliant with RFC5952.
This document lists 4 PHP frameworks: CodeIgniter, Lithify, Silex, and Solar. CodeIgniter and Lithify are full-stack frameworks while Silex is micro and Solar is lightweight. These frameworks provide tools to build PHP web applications and websites.
This document discusses a lightweight programming language called LL Planets. It is written in Java and has a blog located at http://ll.jus.or.jp/blog/ that provides more information about the language.
This document describes Keires_DB, an ORM library for PHP. It provides an object-relational mapping for PostgreSQL databases. Key features include using PDO for database access, late static binding support for PHP 5.3+, and defining database schemas and models through class declarations. Examples demonstrate basic CRUD operations and querying data through both object and raw SQL methods.
This document discusses encoding and decoding of data. It includes 1) an introduction of the author, 2) an agenda covering ID generation and encoding/decoding, 3) a reference to the RFC on base64 encoding, 4) an example of ID generation from a database sequence, and 5) code examples for generating unique hashes and encoding/decoding data using gzip compression and base64url encoding. The document concludes by thanking the reader.
12. •問題の3.3.1節。変更前。
• Applications may only use
Documented APIs in the manner
prescribed by Apple and must not
use or call any private APIs.
12
2010年7月31日土曜日
13. •問題の3.3.1節。変更後。
• Applications may only use Documented APIs in the
manner prescribed by Apple and must not use or call
any private APIs. Applications must be originally
written in Objective-C, C, C++, or JavaScript as
executed by the iPhone OS WebKit engine, and only
code written in C, C++, and Objective-C may
compile and directly link against the Documented
APIs (e.g., Applications that link to Documented APIs
through an intermediary translation or compatibility
layer or tool are prohibited).
13
2010年7月31日土曜日
14. • Applications may only use
Documented APIs in the manner
prescribed by Apple and must not
use or call any private APIs.
• アプリケーションはAppleによって規定さ
れた文書化されたAPIのみを使用でき、プ
ライベートAPIを使用または呼び出しては
ならない。
14
2010年7月31日土曜日
15. • Applications must be originally
written in Objective-C, C, C++, or
JavaScript as executed by the
iPhone OS WebKit engine, ...
• アプリケーションは、iPhone OS
WebKitエンジンによって実行される場合
は、最初から Objective-C, C, C++,
JavaScriptで書かれていなければなら
ず...
15
2010年7月31日土曜日
16. • ... and only code written in C, C++,
and Objective-C may compile and
directly link against the Documented
APIs ...
• また、コンパイルして文書化されたAPIに
直接リンクする場合は C, C++,
Objective-C で書かれていなければなら
ない。
16
2010年7月31日土曜日
17. • (e.g., Applications that link to
Documented APIs through an
intermediary translation or
compatibility layer or tool are
prohibited).
• (例えば、文書化されたAPIに対して、中間
的な変換、互換レイヤー、ツールを用いて
リンクするアプリケーションは、禁止され
る)
17
2010年7月31日土曜日
22. • Unless otherwise approved by Apple in
writing, no interpreted code may be
downloaded or used in an Application
except for code that is interpreted and
run by Apple’s Documented APIs and
built-in interpreter(s). Notwithstanding
the foregoing, with Apple’s prior written
consent, an Application may use
embedded interpreted code in a limited
way if such use is solely for providing
minor features or functionality that are
consistent with the intended and
advertised purpose of the Application.
22
2010年7月31日土曜日