Re:Conversations (XMPP Client) is now a UnifiedPush distributor
by karmanyaahm on Sunday January 15, 2023 @12:33AM
(#34386986)
It is kinda weird. However, at the end of the day, UnifiedPush is just a protocol that allows $heavyProtocolA to receive notifications through $lightProtocolB.
And XMPP is just $lightProtocolB, there is nothing stopping an XMPP-based UnifiedPush distributor w/o messaging from existing. If you don't use XMPP for messaging, there are many simpler distributors available.
Re:Conversations (XMPP Client) is now a UnifiedPush distributor
by WGH_ on Sunday January 15, 2023 @02:56PM
(#34392646)
Is it really about light vs. heavy though? I thought it was mostly about multiplexing notifications through a single app (usually through a single connection as well), so only one app has to consume resources constantly, and others might be activated as needed.
Re:Conversations (XMPP Client) is now a UnifiedPush distributor
by ryukafalz on Monday January 16, 2023 @04:33PM
(#34405777)
It's a little bit of both. You want to only keep one connection open as it minimizes the amount of network activity for e.g. keepalives. You also don't want the app holding that connection open to drain the battery in the process though.
(Trying to wrap my head around the architecture too, with the last sentence there. Presumably the service and client need to know how to talk to the UnifiedPush provider?)