`
daojin
  • 浏览: 690376 次
  • 性别: Icon_minigender_1
  • 来自: 西安
社区版块
存档分类
最新评论

Android学习日记(1)

 
阅读更多
/*
 * Copyright (C) 2006 The Android Open Source Project
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package android.os;

import java.io.FileDescriptor;
import java.io.PrintWriter;

/**
 * Base interface for a remotable object, the core part of a lightweight
 * remote procedure call mechanism designed for high performance when
 * performing in-process and cross-process calls.  This
 * interface describes the abstract protocol for interacting with a
 * remotable object.  Do not implement this interface directly, instead
 * extend from {@link Binder}.
 * 
 * <p>The key IBinder API is {@link #transact transact()} matched by
 * {@link Binder#onTransact Binder.onTransact()}.  These
 * methods allow you to send a call to an IBinder object and receive a
 * call coming in to a Binder object, respectively.  This transaction API
 * is synchronous, such that a call to {@link #transact transact()} does not
 * return until the target has returned from
 * {@link Binder#onTransact Binder.onTransact()}; this is the
 * expected behavior when calling an object that exists in the local
 * process, and the underlying inter-process communication (IPC) mechanism
 * ensures that these same semantics apply when going across processes.
 * 
 * <p>The data sent through transact() is a {@link Parcel}, a generic buffer
 * of data that also maintains some meta-data about its contents.  The meta
 * data is used to manage IBinder object references in the buffer, so that those
 * references can be maintained as the buffer moves across processes.  This
 * mechanism ensures that when an IBinder is written into a Parcel and sent to
 * another process, if that other process sends a reference to that same IBinder
 * back to the original process, then the original process will receive the
 * same IBinder object back.  These semantics allow IBinder/Binder objects to
 * be used as a unique identity (to serve as a token or for other purposes)
 * that can be managed across processes.
 * 
 * <p>The system maintains a pool of transaction threads in each process that
 * it runs in.  These threads are used to dispatch all
 * IPCs coming in from other processes.  For example, when an IPC is made from
 * process A to process B, the calling thread in A blocks in transact() as
 * it sends the transaction to process B.  The next available pool thread in
 * B receives the incoming transaction, calls Binder.onTransact() on the target
 * object, and replies with the result Parcel.  Upon receiving its result, the
 * thread in process A returns to allow its execution to continue.  In effect,
 * other processes appear to use as additional threads that you did not create
 * executing in your own process.
 * 
 * <p>The Binder system also supports recursion across processes.  For example
 * if process A performs a transaction to process B, and process B while
 * handling that transaction calls transact() on an IBinder that is implemented
 * in A, then the thread in A that is currently waiting for the original
 * transaction to finish will take care of calling Binder.onTransact() on the
 * object being called by B.  This ensures that the recursion semantics when
 * calling remote binder object are the same as when calling local objects.
 * 
 * <p>When working with remote objects, you often want to find out when they
 * are no longer valid.  There are three ways this can be determined:
 * <ul>
 * <li> The {@link #transact transact()} method will throw a
 * {@link RemoteException} exception if you try to call it on an IBinder
 * whose process no longer exists.
 * <li> The {@link #pingBinder()} method can be called, and will return false
 * if the remote process no longer exists.
 * <li> The {@link #linkToDeath linkToDeath()} method can be used to register
 * a {@link DeathRecipient} with the IBinder, which will be called when its
 * containing process goes away.
 * </ul>
 * 
 * @see Binder
 */
public interface IBinder {
    /**
     * The first transaction code available for user commands.
     */
    int FIRST_CALL_TRANSACTION  = 0x00000001;
    /**
     * The last transaction code available for user commands.
     */
    int LAST_CALL_TRANSACTION   = 0x00ffffff;
    
    /**
     * IBinder protocol transaction code: pingBinder().
     */
    int PING_TRANSACTION        = ('_'<<24)|('P'<<16)|('N'<<8)|'G';
    
    /**
     * IBinder protocol transaction code: dump internal state.
     */
    int DUMP_TRANSACTION        = ('_'<<24)|('D'<<16)|('M'<<8)|'P';
    
    /**
     * IBinder protocol transaction code: interrogate the recipient side
     * of the transaction for its canonical interface descriptor.
     */
    int INTERFACE_TRANSACTION   = ('_'<<24)|('N'<<16)|('T'<<8)|'F';

    /**
     * Flag to {@link #transact}: this is a one-way call, meaning that the
     * caller returns immediately, without waiting for a result from the
     * callee. Applies only if the caller and callee are in different
     * processes.
     */
    int FLAG_ONEWAY             = 0x00000001;
    
    /**
     * Get the canonical name of the interface supported by this binder.
     */
    public String getInterfaceDescriptor() throws RemoteException;

    /**
     * Check to see if the object still exists.
     * 
     * @return Returns false if the
     * hosting process is gone, otherwise the result (always by default
     * true) returned by the pingBinder() implementation on the other
     * side.
     */
    public boolean pingBinder();

    /**
     * Check to see if the process that the binder is in is still alive.
     *
     * @return false if the process is not alive.  Note that if it returns
     * true, the process may have died while the call is returning.
     */
    public boolean isBinderAlive();
    
    /**
     * Attempt to retrieve a local implementation of an interface
     * for this Binder object.  If null is returned, you will need
     * to instantiate a proxy class to marshall calls through
     * the transact() method.
     */
    public IInterface queryLocalInterface(String descriptor);
    
    /**
     * Print the object's state into the given stream.
     * 
     * @param fd The raw file descriptor that the dump is being sent to.
     * @param args additional arguments to the dump request.
     */
    public void dump(FileDescriptor fd, String[] args) throws RemoteException;
    
    /**
     * Perform a generic operation with the object.
     * 
     * @param code The action to perform.  This should
     * be a number between {@link #FIRST_CALL_TRANSACTION} and
     * {@link #LAST_CALL_TRANSACTION}.
     * @param data Marshalled data to send to the target.  Most not be null.
     * If you are not sending any data, you must create an empty Parcel
     * that is given here.
     * @param reply Marshalled data to be received from the target.  May be
     * null if you are not interested in the return value.
     * @param flags Additional operation flags.  Either 0 for a normal
     * RPC, or {@link #FLAG_ONEWAY} for a one-way RPC.
     */
    public boolean transact(int code, Parcel data, Parcel reply, int flags)
        throws RemoteException;

    /**
     * Interface for receiving a callback when the process hosting an IBinder
     * has gone away.
     * 
     * @see #linkToDeath
     */
    public interface DeathRecipient {
        public void binderDied();
    }

    /**
     * Register the recipient for a notification if this binder
     * goes away.  If this binder object unexpectedly goes away
     * (typically because its hosting process has been killed),
     * then the given {@link DeathRecipient}'s
     * {@link DeathRecipient#binderDied DeathRecipient.binderDied()} method
     * will be called.
     * 
     * <p>You will only receive death notifications for remote binders,
     * as local binders by definition can't die without you dying as well.
     * 
     * @throws Throws {@link RemoteException} if the target IBinder's
     * process has already died.
     * 
     * @see #unlinkToDeath
     */
    public void linkToDeath(DeathRecipient recipient, int flags)
            throws RemoteException;

    /**
     * Remove a previously registered death notification.
     * The recipient will no longer be called if this object
     * dies.
     * 
     * @return Returns true if the <var>recipient</var> is successfully
     * unlinked, assuring you that its
     * {@link DeathRecipient#binderDied DeathRecipient.binderDied()} method
     * will not be called.  Returns false if the target IBinder has already
     * died, meaning the method has been (or soon will be) called.
     * 
     * @throws Throws {@link java.util.NoSuchElementException} if the given
     * <var>recipient</var> has not been registered with the IBinder, and
     * the IBinder is still alive.  Note that if the <var>recipient</var>
     * was never registered, but the IBinder has already died, then this
     * exception will <em>not</em> be thrown, and you will receive a false
     * return value instead.
     */
    public boolean unlinkToDeath(DeathRecipient recipient, int flags);
}
 
分享到:
评论

相关推荐

    android_日记本.zip

    在Android平台上开发一款日记本应用是一项常见的任务,尤其对于初学者和有经验的开发者来说都是一个有趣的实践项目。...这是一个全面的学习项目,可以帮助开发者深入理解Android应用开发的各个方面。

    android学习日记-2 ASM android底层

    【标题】:“Android学习日记-2 ASM android底层” 在Android开发中,深入理解系统的底层运作是提升技术能力的重要环节。ASM是一个强大的字节码操控和分析框架,它允许动态生成类或者增强已有类的功能,而无需知道...

    Android代码-移动日记本功能包含传统的日记本和音频日记视频日记实现私密日记和普通日记。.zip

    在Android平台上,开发一款移动日记本应用是一种常见的实践,它为用户提供了一种便捷的方式来记录他们的日常生活,情感体验,以及重要事件。这款名为"Diary"的应用不仅包含了传统的文本日记功能,还创新性地集成了...

    基于android的日记本

    1. **数据存储**:用户录入的每篇日记都会被转化为结构化的数据存储在SQLite数据库中,包括日记的标题、日期、内容等信息。 2. **数据操作**: - **增加**:当用户新建一篇日记时,应用会通过SQLite的INSERT语句将...

    基于android的个人日记本程序(Sqlite数据库).zip

    《基于Android的个人日记本程序:SQLite数据库应用详解》 ...通过学习和实践此类项目,开发者不仅可以掌握Android应用开发的基础,还能深入理解如何在移动设备上高效、安全地管理数据,为今后的项目开发打下坚实基础。

    Android 日记本学习实例

    总的来说,“Android日记本学习实例”是一个综合性的项目,涵盖了Android开发中的多个重要知识点,包括Activity、Intent、布局设计、SQLite数据库、权限管理和网络通信等。通过这个实例,你可以更深入地理解和掌握...

    android学习日记-4 JAVA注解总结

    本篇“Android学习日记-4 JAVA注解总结”将深入探讨Java注解及其在Android中的应用。 一、Java注解概述 Java注解是一种类型安全的元数据机制,自Java 5引入以来,已经在各种框架和库中广泛应用。注解通过@符号开头...

    android 日记本

    综上所述,"android 日记本"源代码涵盖了Android应用开发的基础,包括UI设计、数据存储、生命周期管理、Intent机制等核心概念,对初学者来说是一个很好的学习资源。通过研究这个项目,不仅可以理解Android应用的基本...

    android学习日记-3 Timer

    这篇博客"android学习日记-3 Timer"深入探讨了`Timer`类的使用方法及其背后的原理。下面将详细阐述`Timer`类的核心概念、工作原理以及如何在Android应用中合理利用它。 `Timer`类是Java提供的一个非线程安全的调度...

    android简易日记本

    总的来说,【Android简易日记本】是一个很好的学习案例,展示了如何在Android平台上利用SQLite数据库进行数据管理,同时结合Android的UI组件和框架实现用户交互。无论是对初学者还是有经验的开发者,都能从中学习到...

    Android应用源码之日记本.zip

    【Android应用源码之日记本.zip】是一个包含Android应用程序源代码的压缩文件,重点在于学习和研究Android开发。这个源码实例很可能是一个简单的日记应用程序,它可以帮助开发者理解如何在Android平台上构建用户友好...

    android-日记本

    《Android版日记本:SQLite数据库的应用与ListView展示》 在移动应用开发中,尤其是...通过学习这个项目,开发者可以深入了解Android数据存储和UI交互的设计思路,为进一步开发更复杂的移动应用打下坚实的基础。

    安卓Android源码——日记本.zip

    通过分析这个源码,我们可以学习到Android应用的基本架构、数据管理、UI设计和权限管理等多个方面的知识,这对于提升Android开发技能大有裨益。如果你希望深入理解Android应用的开发,这将是一个很好的实践案例。

    Android日记本源码

    【Android日记本源码】是一个深入探讨Android应用开发的实例,尤其关注布局设计与数据存储这两方面的技术。在这个项目中,开发者将学习如何构建一个功能齐全的日记应用程序,包括创建用户友好的界面、记录和保存用户...

    Android日记本小程序.rar

    总的来说,通过研究这个【Android日记本小程序】,你可以深入理解Android应用的基本架构,学习到如何创建用户界面、处理数据存储、实现用户交互以及进行应用调试等核心技能。这不仅有助于提升你的编程能力,也为将来...

    Android开发日记本源代码

    通过分析这个“Android开发日记本源代码”,我们可以学习到Android应用的基本架构,数据存储方式,以及如何在Android环境中实现用户交互和后台任务管理。这对于Android开发者来说,是一个很好的实践和学习案例。

    android加密日记本源码

    开发者可以学习如何在Android环境中实现数据加密和解密,以及如何设计基本的日记应用程序界面和功能。 【描述】中的关键知识点包括: 1. **Android应用开发**:这个项目基于Android Studio,使用Java或Kotlin语言...

    Android日记本

    1. **用户界面(UI)设计**:应用的界面美观且易操作,这意味着开发者需要熟练掌握Android Studio中的布局管理器,如LinearLayout、RelativeLayout和ConstraintLayout等,用于构建清晰、直观的用户界面。此外,还...

    简单的基于Android的记事本/日记系统

    "简单的基于Android的记事本/日记系统" 这个标题表明这是一个专为Android平台设计的应用程序,主要用于记录日常笔记或日记。它强调了“简单”,这意味着该应用可能具有用户友好的界面和基本的功能,适合初级开发者...

Global site tag (gtag.js) - Google Analytics