Differential D4803 Diff 13758 src/app/Backends/Events.php

Changeset View

Standalone View

src/app/Backends/Events.php

This file was added.

				<?php

				namespace App\Backends;

				use App\User;
				use Illuminate\Support\Facades\Redis;

				class Events
				{
				/**
				* Pull message for the specified client application.
				* It waits for the new message up to specified time limit.
				*
				* @param string $clientId Client identifier
				* @param int $timeout Timeout in seconds
				*/
				public static function pullMessage(string $clientId, int $timeout)
				{
				$element = Redis::brPop('push:' . $clientId, $timeout);

				if (is_array($element) && is_string($element[1])) {
				return json_decode($element[1]);
				}

				return null;
				}

				/**
				* Push a notification to all clients of a user.
				*
				* @param User $user User object
				* @param string\|array $message Message/data to push
				*
				* @return bool True if message has been pushed to any client, False otherwise
				*/
				public static function pushMessage(User $user, $message, $type = 'message'): bool
				{
				$count = 0;

				$user->companionApps()
				->where('mfa_enabled', true)
				->each(function ($app) use ($message, $type, &$count) {
				if ($app->isPaired()) {
				$count++;
				// FIXME: Should we maybe use oauth_client_id or notification_token?
				mollekopfUnsubmitted Not Done Inline Actions In the firebase case the notification_token is a separate token that identifies the channel to the device. We could implement the same abstraction I suppose: The device registers with a separate "client_id" as notification token. We use the client_id that is stored in the notification token instead of the device_id. There's currently a 1:1 mapping between notification tokens and deviceid, so it doesn't buy us anything atm, but may provide more flexibility in the future? mollekopf: In the firebase case the notification_token is a separate token that identifies the channel to…
				self::pushMessageToClient($app->device_id, $message, $type);
				}
				});

				return $count > 0;
				}

				/**
				* Push a notification to specified client application
				*
				* @param string $clientId Client identifier
				* @param string\|array $message Message/data to push
				* @param string $type Message type
				* @param bool $prepend Prepend the message to the list (not append)
				*/
				public static function pushMessageToClient(string $clientId, $message, $type = 'message', $prepend = false)
				{
				$data = json_encode([
				'type' => $type,
				'data' => $message,
				]);

				$cache_key = 'push:' . $clientId;

				if ($prepend) {
				Redis::lPush($cache_key, $data);
				} else {
				Redis::rPush($cache_key, $data);
				}

				// TODO: How to make these entries to expire? It looks that we can set
				// TTL on the whole list, but not it's elements. I.e. we might need
				// to store expires_on value in the $data and skip them in pullMessage().
				Redis::expire($cache_key, 10 * 60);
				}
				}