replicant-frameworks_native/include/binder
Christopher Tate c811e7a775 Binder linkage no longer depends on JNI objrefs as persistent tokens
There are two areas that have changed to eliminate the assumption that
local jobject references are both canonical and persistent:

1. JavaBBinderHolder no longer holds onto and reuses it parent object
reference per se.  Since the underlying JavaBBinder object holds a
real global ref, this was redundant anyway.  Now, for purposes of its
transient need to perform JNI operations, it simply uses the current
jobject ref(s) passed during method invocation, and no longer attempts
to hold these refs beyond the scope of a single invocation.

2. Binder obituaries no longer assume that a jobject reference to a
recipient will always compare == as a 32-bit value with any future
reference to the same object.  The implementation now asks Dalvik
whether object references match.

Bug 2090115

Change-Id: If62edd554d0a9fbb2d2977b0cbf8ad7cc8e2e68d
2011-02-24 13:15:09 -08:00
..
Binder.h
BinderService.h
BpBinder.h
CursorWindow.h resubmitting Change-Id: I67b1d04a5c9fc18b0cd4da6184d0b814b64d89e9 2010-12-21 09:32:36 -08:00
IBinder.h Binder linkage no longer depends on JNI objrefs as persistent tokens 2011-02-24 13:15:09 -08:00
IInterface.h
IMemory.h
IPCThreadState.h
IPermissionController.h
IServiceManager.h
MemoryBase.h
MemoryDealer.h
MemoryHeapBase.h
MemoryHeapPmem.h
Parcel.h
Permission.h
ProcessState.h