StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhat is the best approach for Android Service and data communication
primarykey
Id
18294812
data
AcceptedAnswerId
18296538
AnswerCount
1
ClosedDate
2013-09-19T12:27:29.143
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-18T01:13:46.910
FavoriteCount
0
LastActivityDate
2013-08-18T06:58:36.563
LastEditDate
LastEditorUserId
0
OwnerUserId
962773
ParentId
0
PostTypeId
1
Score
1
ViewCount
221
LastEditorDisplayName
text
Body
I am looking for the best approach to share data between a service and 2 different clients (an app and a widget). Currently my application kicks off a thread that downloads a large amount of data every 15 seconds or so in the background, stuffs them into an object graph, which is then consumed by the main app on a configurable time interval. This works for the primary app but isn't sufficient for the widget that I want to develop as well, because the object graph will be out of process (and the approach is kind of messy IMO). So I am looking to extract the data retrieval part into a service (or if there is a better suggestion, something else). My question is, what is the best way to communicate the data received from this service with the clients? Or would you not use a service and instead use something else? Because of the overhead on the client, I want the service to notify the clients when data is ready as opposed to the client continuously polling the service.....if possible...of course. I have looked at broadcasting the intent (both app and widget would receive) but I think I have to serialize the entire object graph and then inflate it in the client in order to do that. Is that correct? I am concerned with the speed at which I can accomplish the re-inflate client side. Is there a better way to ship the data back to the clients? I would prefer to ship the objects if that is possible and not serialize...but if that is the best way, then I will do it. Any help is greatly appreciated!
Tags
<android><broadcastreceiver><android-service>
Title
What is the best approach for Android Service and data communication
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMichael Stoner
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.