What about service and broadcast?

[Melonpi]

I've seen some MVP implementations, but no one talks about long running service(e.g. media player) and system broadcast.
They are created with context, so they should be placed in model layer or something?
Is there any reference we can get?
And thanks for your great work, this repo is so helpful.

[Juude]

for broadcast
when we talk about MVP, that does not mean that there are only M, V, and P in the code. we also need to communicate between the three layers, in this code repository, we use interface to communicate, but we can also use broadcast and otto to communicate between different layers.

for service
Because service has no ui, we often use Service as the P and M, for example in a audio player, we use a Service to listen to UI actions and play/pause the music, we also use Service to access our playlists that is Model.

[Melonpi]

Thanks for your reply.
I think most question is about classes need a context and lifecycle always binding to an activity.

For broadcast
sry for the misleading, I mean system broadcast and broadcast receivers with context.
Rxbus or otto may be a good choice. For system broadcast receiver, make it just as a publisher for system broadcast may be a good practice.
So it can be hold directly by activity or presenter,and make tests in presenter by mock events?

For service
Presenters is mean to has no aware of context to make test easier. But as you said, service be a presenter may also contains so business logic, maybe there should be one more layer?
A service control audio player and also saving/loading data may be too heavy.

One more thing, do u have any occasion to let one view has multi presenters?

[ghost]

Why don't we create s new architecture for these needs , #115