3e2fb7056a
There is no difference and has never really been a difference between local-only and remotable CursorWindows. By removing the distinction officially in the API, we will make it easier to implement CrossProcessCursor correctly. CrossProcessCursor is problematic currently because it's not clear whether a call to getWindow() will return a local-only window or a remotable window. As a result, the bulk cursor adaptor has special case handling for AbstractWindowedCursors vs. ordinary CrossProcessCursors so that it can set a remotable window before the cursor fills it. All these problems go away if we just forget about local-only windows being special in any way. Change-Id: Ie59f517968e33d0ecb239c3c4f60206495e8f376 |
||
---|---|---|
.. | ||
Android.mk | ||
Binder.cpp | ||
BpBinder.cpp | ||
CursorWindow.cpp | ||
IInterface.cpp | ||
IMemory.cpp | ||
IPCThreadState.cpp | ||
IPermissionController.cpp | ||
IServiceManager.cpp | ||
MemoryBase.cpp | ||
MemoryDealer.cpp | ||
MemoryHeapBase.cpp | ||
MemoryHeapPmem.cpp | ||
Parcel.cpp | ||
PermissionCache.cpp | ||
ProcessState.cpp | ||
Static.cpp |