readme

README.md

@@ -28,15 +28,15 @@ The package could be installed with [Composer](https://getcomposer.org):
 composer require yiisoft/queue
 ```
 
-## Ready for yiisoft/config
+## Ready for Yii Config
 
 If you are using [yiisoft/config](https://github.com/yiisoft/config), you'll find out this package has some defaults
 in the [`common`](config/di.php) and [`params`](config/params.php) configurations saving your time. Things you should
 change to start working with the queue:
 
 - Optionally: define default `\Yiisoft\Queue\Adapter\AdapterInterface` implementation.
-- And/or define channel-specific `AdapterInterface` implementations in the `channel-definitions` params key to be used
-  with the [queue factory](#different-queue-channels).
+- And/or define channel-specific `AdapterInterface` implementations in the `channel` params key to be used
+  with the [queue provider](#different-queue-channels).
 - Define [message handlers](docs/guide/worker.md#handler-format) in the `handlers` params key to be used with the `QueueWorker`.
 - Resolve other `\Yiisoft\Queue\Queue` dependencies (psr-compliant event dispatcher).
 
@@ -136,15 +136,24 @@ $status->isDone();
 
 ## Different queue channels
 
-Often we need to push to different queue channels with an only application. There is the `QueueFactory` class to make
-different `Queue` objects creation for different channels. With this factory channel-specific `Queue` creation is as
-simple as
+Often we need to push to different queue channels with an only application. There is the `QueueProviderInterface`
+interface that provides different `Queue` objects creation for different channels. With implementation of this interface
+channel-specific `Queue` creation is as simple as
 
 ```php
-$queue = $factory->get('channel-name');
+$queue = $provider->get('channel-name');
 ```
 
-The main usage strategy is with explicit definition of channel-specific adapters. Definitions are passed in
+Out of the box, there are four implementations of the `QueueProviderInterface`:
+
+- `AdapterFactoryQueueProvider`
+- `QueueFactoryQueueProvider`
+- `PrototypeQueueProvider`
+- `CompositeQueueProvider`
+
+### `AdapterFactoryQueueProvider`
+
+Provider based on definition of channel-specific adapters. Definitions are passed in
 the `$definitions` constructor parameter of the factory, where keys are channel names and values are definitions
 for the [`Yiisoft\Factory\Factory`](https://github.com/yiisoft/factory). Below are some examples:
 
@@ -163,19 +172,23 @@ use Yiisoft\Queue\Adapter\SynchronousAdapter;
 
 For more information about a definition formats available see the [factory](https://github.com/yiisoft/factory) documentation.
 
-Another queue factory usage strategy is implicit adapter creation via `withChannel()` method call. To use this approach
-you should pass some specific constructor parameters:
+### `QueueFactoryQueueProvider`
 
-- `true` to the `$enableRuntimeChannelDefinition`
-- a default `AdapterInterface` implementation to the `$defaultAdapter`.
+Provider is similar to `AdapterFactoryQueueProvider`, but it uses definitions of channel-specific queues.
 
-In this case `$factory->get('channel-name')` call will be converted
-to `$this->queue->withAdapter($this->defaultAdapter->withChannel($channel))`, when there is no explicit adapter definition
-in the `$definitions`.
+### `PrototypeQueueProvider`
+
+Queue provider that only changes the channel name of the base queue. It can be useful when your queues used the same
+adapter.
 
 > Warning: This strategy is not recommended as it does not give you any protection against typos and mistakes
 > in channel names.
 
+### `CompositeQueueProvider`
+
+This provider allows you to combine multiple providers into one. It will try to get a queue from each provider in the
+order they are passed to the constructor. The first queue found will be returned.
+
 ## Console execution
 
 The exact way of task execution depends on the adapter used. Most adapters can be run using

config/di.php

@@ -19,7 +19,7 @@
 use Yiisoft\Queue\Middleware\Push\MiddlewareFactoryPush;
 use Yiisoft\Queue\Middleware\Push\MiddlewareFactoryPushInterface;
 use Yiisoft\Queue\Middleware\Push\PushMiddlewareDispatcher;
-use Yiisoft\Queue\Provider\QueueFactoryQueueProvider;
+use Yiisoft\Queue\Provider\AdapterFactoryQueueProvider;
 use Yiisoft\Queue\Provider\QueueProviderInterface;
 use Yiisoft\Queue\Queue;
 use Yiisoft\Queue\QueueInterface;
@@ -30,7 +30,7 @@
 
 return [
     QueueProviderInterface::class => [
-        'class' => QueueFactoryQueueProvider::class,
+        'class' => AdapterFactoryQueueProvider::class,
         '__construct()' => [
             'definitions' => $params['yiisoft/queue']['channels'],
         ],

config/params.php

@@ -2,13 +2,15 @@
 
 declare(strict_types=1);
 
+use Yiisoft\Queue\Adapter\AdapterInterface;
 use Yiisoft\Queue\Command\ListenAllCommand;
 use Yiisoft\Queue\Command\ListenCommand;
 use Yiisoft\Queue\Command\RunCommand;
 use Yiisoft\Queue\Debug\QueueCollector;
 use Yiisoft\Queue\Debug\QueueProviderInterfaceProxy;
 use Yiisoft\Queue\Debug\QueueWorkerInterfaceProxy;
 use Yiisoft\Queue\Provider\QueueProviderInterface;
+use Yiisoft\Queue\Queue;
 use Yiisoft\Queue\Worker\WorkerInterface;
 
 return [
@@ -21,7 +23,9 @@
     ],
     'yiisoft/queue' => [
         'handlers' => [],
-        'channels' => [],
+        'channels' => [
+            Queue::DEFAULT_CHANNEL_NAME => AdapterInterface::class,
+        ],
         'middlewares-push' => [],
         'middlewares-consume' => [],
         'middlewares-fail' => [],