# Questions about mezzio-swoole, everytime I refresh the page, title reduplicated one more time!
**URL:** https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121
**Category:** Mezzio
**Tags:** mezzio-swoole
**Created:** [February 20, 2021, 6:42am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121 "2021-02-20T06:42:19Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [February 20, 2021, 6:42am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/1 "2021-02-20T06:42:19Z")
Pls check this webiste [http://www.mm3bb.com/](http://www.mm3bb.com/)
It is a brand-new skeleton, every time I refresh the home page, the title repeat one more time.
like
`Home - mezzio 1st time visit`
`Home - mezzio - Home - mezzio 2nd time visit`
`Home - mezzio - Home - mezzio - Home - mezzio 3rd time visit`
…
That’s ridiculous! I don’t know what’s going wrong.
Anybody can tell me why?
---
### Author:  [@acelaya](https://discourse.laminas.dev/u/acelaya)
#### Post date: [February 20, 2021, 8:11pm UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/2 "2021-02-20T20:11:51Z")
Most probably the problem is that the template renderer is not stateless, but keeping bits of information inside of it.
When you serve an app with php-fpm, a new process is spinned-up for every request, which makes this kind of things pass unnoticed.
However, since swoole keeps services in memory and reuses them between requests, if you append a title on every request, they can end up getting merged.
This is documented and you can find some ways to work around it here: [Considerations when using Swoole - mezzio-swoole - Laminas Docs](https://docs.mezzio.dev/mezzio-swoole/v3/considerations/#stateless-services)
---
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [February 22, 2021, 1:09am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/3 "2021-02-22T01:09:46Z")
Thanks for your kind reply! But I am not familar with the mezzio-swoole framework. The swoole-kind framework works so much different from the php-fpm kind.
I am just trying to apply mezzio-swoole to do stuff. I didn’t think about that I will encounter problems when I just install the official framework skeleton.
In my plan, I first install the official skeleton, then change it little by little, at least I can edit the view, it should be safe.
> [@acelaya](#):
>
> However, since swoole keeps services in memory and reuses them between requests, if you append a title on every request, they can end up getting merged.
I didn’t append a title to every request, If I remove this, then the webpage have no title at all. I don’t know how to deal with this.
---
### Author:  [@marcguyer](https://discourse.laminas.dev/u/marcguyer)
#### Post date: [February 22, 2021, 5:45pm UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/4 "2021-02-22T17:45:07Z")
> [@jobsfan](#):
>
> The swoole-kind framework works so much different from the php-fpm kind.
This is the key. Swoole is quite new and works in a fundamentally different way. You must understand that difference in order to understand why you’re seeing this behavior. You’re likely to run into it again, if you’re going to use Swoole, so I recommend studying up on that. @acelaya gave a good overview and linked to a place to get started. Php is going stateless but it’s not going to happen overnight.
---
### Author:  [@george](https://discourse.laminas.dev/u/george)
#### Post date: [February 23, 2021, 8:54am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/5 "2021-02-23T08:54:03Z")
The head-title view helpers use a stateful container. I normally inject a middleware that resets all of the laminas view helpers affected for every request. Head title, head link, head script etc.
Here’s a link to something a bit old that I found - it refers to the Zend equivalents.
>
---
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [March 16, 2021, 6:19am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/6 "2021-03-16T06:19:50Z")
Where this middleware file locate?
---
### Author:  [@george](https://discourse.laminas.dev/u/george)
#### Post date: [March 16, 2021, 8:40am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/7 "2021-03-16T08:40:50Z")
It’s something I wrote for a private project that gets inserted into the main pipeline.
---
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [March 25, 2021, 8:47am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/8 "2021-03-25T08:47:32Z")
@george, thanks for your kind reply! However I still have problem with it.
---
### Author:  [@george](https://discourse.laminas.dev/u/george)
#### Post date: [March 25, 2021, 9:11am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/9 "2021-03-25T09:11:04Z")
There are a few things there that need looking at.
First of all, you’ve piped the middleware after the NotFoundHandler so it will never execute. Ideally, this middleware would execute either before or after every request that renders a view, so before DispatchMiddleware or after it would work.
You also don’t appear to have setup a factory for the middleware. You can see from its constructor that it has a dependency on the HelperPluginManager, so you will need to create a factory that looks something like:
```php
class ResetViewHelpersFactory {
public function __invoke(ContainerInterface $container) : ViewHelperResetMiddleware
{
return new ViewHelperResetMiddleware(
$container->get(HelperPluginManager::class
);
}
}
```
_(Namespaces and use statements omitted for brevity)_
Don’t forget that you must “Wire up” the factory in your configuration under `$config['dependencies']['factories']`
Without a factory to correctly construct the middleware, you’d receive 'ServiceCantBeCreated` exceptions for every request.
Hope that helps!
---
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [March 25, 2021, 9:40am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/10 "2021-03-25T09:40:17Z")
@george
I followed your steps, maybe I missed something, still not work for me.
---
### Author:  [@george](https://discourse.laminas.dev/u/george)
#### Post date: [March 25, 2021, 11:22am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/11 "2021-03-25T11:22:07Z")
Silly me - you probably need to pipe _before_ dispatch because your template renderer will likely return a response.
Also, you will need to import the HelperPluginManager in your factory - i.e. use Laminas\View\…
---
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [March 25, 2021, 1:53pm UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/12 "2021-03-25T13:53:09Z")
@george Thank you so much! It works!! Yes, you are right! When I move the middleware before the dispatch one in the pipeline, it finally works right.
Still I have a question, the viewhelperresetmiddleware is a uniform middleware which can be used all over the entire project. If there need a middleware only use in somewhere with a narrow scope inside the project, or just need to use in one controller, where should I register the dependency, and where should I inster the middleware? It should not be in the main pipeline because it is not a project-wide used middleware. Many thanks!
---
### Author:  [@george](https://discourse.laminas.dev/u/george)
#### Post date: [March 25, 2021, 2:43pm UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/13 "2021-03-25T14:43:19Z")
Glad you got it working 😃
Typically, what I do, and there are lots of ways to do it… I create an empty interface such as `\App\Pipeline\SpecificCollectionOfMiddleware` and then create a factory for it that returns a `MiddlewarePipe` - I think that’s a `\Laminas\Stratigility\MiddlewarePipe` if memory serves.
Once that is setup, I reference the interface name in the routes that are applicable to the pipeline, so inside your route configuration, you might have something that looks like `$application>get(‘/path/to/thing’, SpecificCollectionOfMiddleware::class, ... route name etc);`
Also because pipelines are middleware themselves, you can use this approach to create chunks of re-usable middleware chains if that makes sense?
---
### Author:  [@jobsfan](https://discourse.laminas.dev/u/jobsfan)
#### Post date: [March 29, 2021, 9:38am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/14 "2021-03-29T09:38:58Z")
@george
Thanks for your kindly reply!
> [@george](#):
>
> `MiddlewarePipe` - I think that’s a `\Laminas\Stratigility\MiddlewarePipe` if memory serves
What do you mean by promoting the conception “MiddlewarePipe”? Is it a special middleware? Or all the middleware are pipes? I am a little confused. I only get to know the pipline conception in django.
In my point of view pipe connected one after another to make the process flowing through.
Besides, in mezzio, the route arrange one reflect to another, not like laminas mvc framework, which can use route tree strategy to match a batch uri. Can I understand it like that?
---
### Author:  [@george](https://discourse.laminas.dev/u/george)
#### Post date: [March 29, 2021, 11:14am UTC](https://discourse.laminas.dev/t/questions-about-mezzio-swoole-everytime-i-refresh-the-page-title-reduplicated-one-more-time/2121/15 "2021-03-29T11:14:36Z")
When you setup a routes to show, create, edit or delete an album for example, inside your routing setup you might have something like this:
```php
$app->get('/show', ShowAlbumHandler::class, 'show');
$app->get('/edit', EditAlbumHandler::class, 'edit');
$app->get('/delete', DeleteAlbumHandler::class, 'delete');
```
As things progress and you want to authenticate users of those routes, you’d need something like:
```php
$app->get('/show', [OnlyAuthenticated::class, ShowAlbumHandler::class], 'show');
$app->get('/edit', [OnlyAuthenticated::class, EditAlbumHandler::class], 'edit');
$app->get('/delete', [OnlyAuthenticated::class, DeleteAlbumHandler::class], 'delete');
```
Perhaps later on you also want to restrict the IP address, but instead of prepending another middleware to all 3 routes, such as `IPRestrictMiddleware::class`, you create a pipeline something like this:
```php
use Laminas\Stratigility\MiddlewarePipeInterface;
use Mezzio\MiddlewareFactory;
final class SomePipelineFactory {
public function __invoke(ContainerInterface $container) : MiddlewarePipeInterface
{
$factory = $container->get(MiddlewareFactory::class);
return $factory->pipeline([
IPRestrictMiddleware::class,
OnlyAuthenticated::class,
]);
}
}
```
I personally like to create marker interfaces for specific pipelines that look something like:
```php
use Laminas\Stratigility\MiddlewarePipeInterface;
interface SomePipeline extends MiddlewarePipeInterface
{
}
```
… so that in config I have
```php
'dependencies' => [
'factories' => [
SomePipeline::class => SomePipelineFactory::class,
],
],
```
Finally, in my routing setup, I can say:
```php
$app->get('/show', [SomePipeline::class, ShowAlbumHandler::class], 'show');
$app->get('/edit', [SomePipeline::class, EditAlbumHandler::class], 'edit');
$app->get('/delete', [SomePipeline::class, DeleteAlbumHandler::class], 'delete');
```
So, that’s what I meant - A convenient way of referring to and composing collections of middleware when you have multiple uses for the same functionality.