Skip to content
This repository has been archived by the owner on Apr 23, 2023. It is now read-only.

Migrate client management from service to fused location api implementation #182

Merged
merged 13 commits into from Apr 19, 2017

Conversation

ecgreb
Copy link
Collaborator

@ecgreb ecgreb commented Apr 18, 2017

Overview

As a prerequisite to adding IPC support (#173), all non-parcelable objects must be removed from the FusedLocationProviderService interface. This patch removes all instances of the LostApiClient as a parameter from FusedLocationProviderService methods and migrates client management into FusedLocationProviderApiImpl.

Proposed Changes

  • Removes all instances of LostApiClient from FusedLocationProviderService interface.
  • Adds direct integration between FusedLocationProviderApiImpl and LostClientManager to add/remove listeners, callbacks, and pending intents.
  • Removes additional deprecated methods for location provider enabled/disabled.
  • Removes explicit start/stop of service relying on bind/unbind only.
  • Renames FusedLocationProviderServiceImpl -> FusedLocationProviderServiceDelegate since this class does not implement an interface but rather follows the delegation pattern using composition.

http://best-practice-software-engineering.ifs.tuwien.ac.at/patterns/delegation.html

@ecgreb ecgreb force-pushed the 173-binder-proxy-class-cast-exception branch from be66968 to ab702be Compare April 18, 2017 22:20
@ecgreb ecgreb changed the title [WIP] Migrate client management from service to fused location api implementation Migrate client management from service to fused location api implementation Apr 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants