forked from zendframework/zendframework
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Zend_EventManager-EventManager.xml
845 lines (720 loc) · 33.4 KB
/
Zend_EventManager-EventManager.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
<?xml version="1.0" encoding="UTF-8"?>
<!-- Reviewed: no -->
<section xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="zend.event-manager.event-manager">
<info><title>The EventManager</title></info>
<section xml:id="zend.event-manager.event-manager.intro">
<info><title>Overview</title></info>
<para>
The <classname>EventManager</classname> is a component designed for the following use
cases:
</para>
<itemizedlist>
<listitem>
<para>
Implementing simple subject/observer patterns.
</para>
</listitem>
<listitem>
<para>
Implementing Aspect-Oriented designs.
</para>
</listitem>
<listitem>
<para>
Implementing event-driven architectures.
</para>
</listitem>
</itemizedlist>
<para>
The basic architecture allows you to attach and detach listeners to named events, both on
a per-instance basis as well as statically; trigger events; and interrupt execution of
listeners.
</para>
</section>
<section xml:id="zend.event-manager.event-manager.quick-start">
<info><title>Quick Start</title></info>
<para>
Typically, you will compose an <classname>EventManager</classname> instance in a class.
</para>
<programlisting language="php"><![CDATA[
use Zend\EventManager\EventCollection,
Zend\EventManager\EventManager;
class Foo
{
protected $events;
public function events(EventCollection $events = null)
{
if (null !== $events) {
$this->events = $events;
} elseif (null === $this->events) {
$this->events = new EventManager(__CLASS__);
}
return $this->events;
}
}
]]></programlisting>
<para>
The above allows users to access the <classname>EventManager</classname> instance, or
reset it with a new instance; if one does not exist, it will be lazily instantiated
on-demand.
</para>
<para>
An <classname>EventManager</classname> is really only interesting if it triggers some
events. Basic triggering takes three arguments: the event name, which is usually the
current function/method name; the "context", which is usually the current object
instance; and the arguments, which are usually the arguments provided to the current
function/method.
</para>
<programlisting language="php"><![CDATA[
class Foo
{
// ... assume events definition from above
public function bar($baz, $bat = null)
{
$params = compact('baz', 'bat');
$this->events()->trigger(__FUNCTION__, $this, $params);
}
}
]]></programlisting>
<para>
In turn, triggering events is only interesting if something is listening for the event.
Listeners attach to the <classname>EventManager</classname>, specifying a named event
and the callback to notify. The callback receives an <classname>Event</classname>
object, which has accessors for retrieving the event name, context, and parameters.
Let's add a listener, and trigger the event.
</para>
<programlisting language="php"><![CDATA[
use Zend\Log\Factory as LogFactory;
$log = LogFactory($someConfig);
$foo = new Foo();
$foo->events()->attach('bar', function ($e) use ($log) {
$event = $e->getName();
$target = get_class($e->getTarget());
$params = json_encode($e->getParams());
$log->info(sprintf(
'%s called on %s, using params %s',
$event,
$target,
$params
));
});
// Results in log message:
$foo->bar('baz', 'bat');
// reading: bar called on Foo, using params {"baz" : "baz", "bat" : "bat"}"
]]></programlisting>
<para>
Note that the second argument to <methodname>attach()</methodname> is any valid callback;
an anonymous function is shown in the example in order to keep the example
self-contained. However, you could also utilize a valid function name, a functor, a
string referencing a static method, or an array callback with a named static method or
instance method. Again, any PHP callback is valid.
</para>
<para>
Sometimes you may want to specify listeners without yet having an object instance of the
class composing an <classname>EventManager</classname>. The
<classname>StaticEventManager</classname> allows you to do this. The call to
<methodname>attach</methodname> is identical to the <classname>EventManager</classname>,
but expects an additional parameter at the beginning: a named instance. Remember the
example of composing an <classname>EventManager</classname>, how we passed it
<constant>__CLASS__</constant>? That value, or any strings you provide in an array to
the constructor, may be used to identify an instance when using the
<classname>StaticEventManager</classname>. As an example, we could change the above
example to attach statically:
</para>
<programlisting language="php"><![CDATA[
use Zend\EventManager\StaticEventManager,
Zend\Log\Factory as LogFactory;
$log = LogFactory($someConfig);
$events = StaticEventManager::getInstance();
$events->attach('Foo', 'bar', function ($e) use ($log) {
$event = $e->getName();
$target = get_class($e->getTarget());
$params = json_encode($e->getParams());
$log->info(sprintf(
'%s called on %s, using params %s',
$event,
$target,
$params
));
});
// Later, instantiate Foo:
$foo = new Foo();
// And we can still trigger the above event:
$foo->bar('baz', 'bat');
// results in log message:
// bar called on Foo, using params {"baz" : "baz", "bat" : "bat"}"
]]></programlisting>
<para>
The <classname>EventManager</classname> also provides the ability to detach listeners,
short-circuit execution of an event either from within a listener or by testing return
values of listeners, test and loop through the results returned by listeners, prioritize
listeners, and more. Many of these features are detailed in the examples.
</para>
<section xml:id="zend.event-manager.event-manager.quick-start.wildcard">
<info><title>Wildcard Listeners</title></info>
<para>
Sometimes you'll want to attach the same listener to many events or to all events of
a given instance -- or potentially, with the static manager, many contexts, and many
events. The <classname>EventManager</classname> component allows for this.
</para>
<example xml:id="zend.event-manager.event-manager.quick-start.wildcard.many">
<info><title>Attaching to many events at once</title></info>
<programlisting language="php"><![CDATA[
$events = new EventManager();
$events->attach(array('these', 'are', 'event', 'names'), $callback);
]]></programlisting>
<para>
Note that if you specify a priority, that priority will be used for all events
specified.
</para>
</example>
<example xml:id="zend.event-manager.event-manager.quick-start.wildcard.wildcard">
<info><title>Attaching using the wildcard</title></info>
<programlisting language="php"><![CDATA[
$events = new EventManager();
$events->attach('*', $callback);
]]></programlisting>
<para>
Note that if you specify a priority, that priority will be used for this
listener for any event triggered.
</para>
<para>
What the above specifies is that <emphasis>any</emphasis> event triggered will
result in notification of this particular listener.
</para>
</example>
<example xml:id="zend.event-manager.event-manager.quick-start.wildcard.static-many">
<info><title>Attaching to many events at once via the StaticEventManager</title></info>
<programlisting language="php"><![CDATA[
$events = StaticEventManager::getInstance();
// Attach to many events on the context "foo"
$events->attach('foo', array('these', 'are', 'event', 'names'), $callback);
// Attach to many events on the contexts "foo" and "bar"
$events->attach(array('foo', 'bar'), array('these', 'are', 'event', 'names'), $callback);
]]></programlisting>
<para>
Note that if you specify a priority, that priority will be used for all events
specified.
</para>
</example>
<example xml:id="zend.event-manager.event-manager.quick-start.wildcard.static-wildcard">
<info><title>Attaching to many events at once via the StaticEventManager</title></info>
<programlisting language="php"><![CDATA[
$events = StaticEventManager::getInstance();
// Attach to all events on the context "foo"
$events->attach('foo', '*', $callback);
// Attach to all events on the contexts "foo" and "bar"
$events->attach(array('foo', 'bar'), '*', $callback);
]]></programlisting>
<para>
Note that if you specify a priority, that priority will be used for all events
specified.
</para>
<para>
The above is specifying that for the contexts "foo" and "bar", the specified
listener should be notified for any event they trigger.
</para>
</example>
</section>
</section>
<section xml:id="zend.event-manager.event-manager.options">
<info><title>Configuration Options</title></info>
<variablelist>
<title>EventManager Options</title>
<varlistentry>
<term>identifier</term>
<listitem>
<para>
A string or array of strings to which the given
<classname>EventManager</classname> instance can answer when accessed via
the <classname>StaticEventManager</classname>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>event_class</term>
<listitem>
<para>
The name of an alternate <classname>Event</classname> class to use for
representing events passed to listeners.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>static_connections</term>
<listitem>
<para>
An instance of a <interfacename>StaticEventCollection</interfacename>
instance to use when triggering events. By default, this will use
the global <classname>StaticEventManager</classname> instance, but that can
be overridden by passing a value to this method. A <constant>null</constant>
value will prevent the instance from triggering any further statically
attached listeners.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="zend.event-manager.event-manager.methods">
<info><title>Available Methods</title></info>
<variablelist>
<varlistentry xml:id="zend.event-manager.event-manager.methods.constructor">
<term>__construct</term>
<listitem>
<methodsynopsis>
<methodname>__construct</methodname>
<methodparam>
<funcparams>null|string|int $identifier</funcparams>
</methodparam>
</methodsynopsis>
<para>
Constructs a new <classname>EventManager</classname> instance, using the
given identifier, if provided, for purposes of static attachment.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.set-event-class">
<term>setEventClass</term>
<listitem>
<methodsynopsis>
<methodname>setEventClass</methodname>
<methodparam>
<funcparams>string $class</funcparams>
</methodparam>
</methodsynopsis>
<para>
Provide the name of an alternate <classname>Event</classname> class to use
when creating events to pass to triggered listeners.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.set-static-connections">
<term>setStaticConnections</term>
<listitem>
<methodsynopsis>
<methodname>setStaticConnections</methodname>
<methodparam>
<funcparams>StaticEventCollection $connections = null</funcparams>
</methodparam>
</methodsynopsis>
<para>
An instance of a <interfacename>StaticEventCollection</interfacename>
instance to use when triggering events. By default, this will use
the global <classname>StaticEventManager</classname> instance, but that can
be overridden by passing a value to this method. A <constant>null</constant>
value will prevent the instance from triggering any further statically
attached listeners.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.get-static-connections">
<term>getStaticConnections</term>
<listitem>
<methodsynopsis>
<methodname>getStaticConnections</methodname>
<void/>
</methodsynopsis>
<para>
Returns the currently attached
<interfacename>StaticEventCollection</interfacename> instance, lazily
retrieving the global <classname>StaticEventManager</classname> instance if
none is attached and usage of static listeners hasn't been disabled by
passing a <constant>null</constant> value to <link
linkend="zend.event-manager.event-manager.methods.set-static-connections">setStaticConnections()</link>.
Returns either a boolean <constant>false</constant> if static listeners are
disabled, or a <interfacename>StaticEventCollection</interfacename> instance
otherwise.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.trigger">
<term>trigger</term>
<listitem>
<methodsynopsis>
<methodname>trigger</methodname>
<methodparam>
<funcparams>string $event, mixed $target, mixed $argv, callback $callback</funcparams>
</methodparam>
</methodsynopsis>
<para>
Triggers all listeners to a named event. The recommendation is to use the
current function/method name for <varname>$event</varname>, appending it
with values such as ".pre", ".post", etc. as needed.
<varname>$context</varname> should be the current object instance, or the
name of the function if not triggering within an object.
<varname>$params</varname> should typically be an associative array or
<classname>ArrayAccess</classname> instance; we recommend using the
parameters passed to the function/method (<function>compact()</function> is
often useful here). This method can also take a callback and behave in the
same way as <methodname>triggerUntil()</methodname>.
</para>
<para>
The method returns an instance of <classname>ResponseCollection</classname>,
which may be used to introspect return values of the various listeners, test
for short-circuiting, and more.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.trigger-until">
<term>triggerUntil</term>
<listitem>
<methodsynopsis>
<methodname>triggerUntil</methodname>
<methodparam>
<funcparams>string $event, mixed $context, mixed $argv, callback
$callback</funcparams>
</methodparam>
</methodsynopsis>
<para>
Triggers all listeners to a named event, just like <link
linkend="zend.event-manager.event-manager.methods.trigger">trigger()</link>,
with the addition that it passes the return value from each listener to
<varname>$callback</varname>; if <varname>$callback</varname> returns a
boolean <constant>true</constant> value, execution of the listeners is
interrupted. You can test for this using <code>$result->stopped()</code>.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.attach">
<term>attach</term>
<listitem>
<methodsynopsis>
<methodname>attach</methodname>
<methodparam>
<funcparams>string $event, callback $callback, int $priority</funcparams>
</methodparam>
</methodsynopsis>
<para>
Attaches <varname>$callback</varname> to the
<classname>EventManager</classname> instance, listening for the event
<varname>$event</varname>. If a <varname>$priority</varname> is provided,
the listener will be inserted into the internal listener stack using that
priority; higher values execute earliest. (Default priority is "1", and
negative priorities are allowed.)
</para>
<para>
The method returns an instance of
<classname>Zend\Stdlib\CallbackHandler</classname>; this value can later be
passed to <methodname>detach()</methodname> if desired.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.attach-aggregate">
<term>attachAggregate</term>
<listitem>
<methodsynopsis>
<methodname>attachAggregate</methodname>
<methodparam>
<funcparams>string|ListenerAggregate $aggregate</funcparams>
</methodparam>
</methodsynopsis>
<para>
If a string is passed for <varname>$aggregate</varname>, instantiates that
class. The <varname>$aggregate</varname> is then passed the
<classname>EventManager</classname> instance to its
<methodname>attach()</methodname> method so that it may register listeners.
</para>
<para>
The <classname>ListenerAggregate</classname> instance is returned.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.detach">
<term>detach</term>
<listitem>
<methodsynopsis>
<methodname>detach</methodname>
<methodparam>
<funcparams>CallbackHandler $listener</funcparams>
</methodparam>
</methodsynopsis>
<para>
Scans all listeners, and detaches any that match <varname>$listener</varname>
so that they will no longer be triggered.
</para>
<para>
Returns a boolean <constant>true</constant> if any listeners have been
identified and unsubscribed, and a boolean <constant>false</constant>
otherwise.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.detach-aggregate">
<term>detachAggregate</term>
<listitem>
<methodsynopsis>
<methodname>detachAggregate</methodname>
<methodparam>
<funcparams>ListenerAggregate $aggregate</funcparams>
</methodparam>
</methodsynopsis>
<para>
Loops through all listeners of all events to identify listeners that are
represented by the aggregate; for all matches, the listeners will be removed.
</para>
<para>
Returns a boolean <constant>true</constant> if any listeners have been
identified and unsubscribed, and a boolean <constant>false</constant>
otherwise.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.get-events">
<term>getEvents</term>
<listitem>
<methodsynopsis>
<methodname>getEvents</methodname>
<void/>
</methodsynopsis>
<para>
Returns an array of all event names that have listeners attached.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.get-listeners">
<term>getListeners</term>
<listitem>
<methodsynopsis>
<methodname>getListeners</methodname>
<methodparam>
<funcparams>string $event</funcparams>
</methodparam>
</methodsynopsis>
<para>
Returns a <classname>Zend\Stdlib\PriorityQueue</classname> instance of all
listeners attached to <varname>$event</varname>.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.clear-listeners">
<term>clearListeners</term>
<listitem>
<methodsynopsis>
<methodname>clearListeners</methodname>
<methodparam>
<funcparams>string $event</funcparams>
</methodparam>
</methodsynopsis>
<para>
Removes all listeners attached to <varname>$event</varname>.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="zend.event-manager.event-manager.methods.prepare-args">
<term>prepareArgs</term>
<listitem>
<methodsynopsis>
<methodname>prepareArgs</methodname>
<methodparam>
<funcparams>array $args</funcparams>
</methodparam>
</methodsynopsis>
<para>
Creates an <classname>ArrayObject</classname> from the provided
<varname>$args</varname>. This can be useful if you want yours listeners
to be able to modify arguments such that later listeners or the triggering
method can see the changes.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="zend.event-manager.event-manager.examples">
<info><title>Examples</title></info>
<example xml:id="zend.event-manager.event-manager.examples.modifying-args">
<info><title>Modifying Arguments</title></info>
<para>
Occasionally it can be useful to allow listeners to modify the arguments they
receive so that later listeners or the calling method will receive those changed
values.
</para>
<para>
As an example, you might want to pre-filter a date that you know will arrive as a
string and convert it to a <classname>DateTime</classname> argument.
</para>
<para>
To do this, you can pass your arguments to <methodname>prepareArgs()</methodname>,
and pass this new object when triggering an event. You will then pull that value
back into your method.
</para>
<programlisting language="php"><![CDATA[
class ValueObject
{
// assume a composed event manager
function inject(array $values)
{
$argv = compact('values');
$argv = $this->events()->prepareArgs($argv);
$this->events()->trigger(__FUNCTION__, $this, $argv);
$date = isset($argv['values']['date']) ? $argv['values']['date'] : new DateTime('now');
// ...
}
}
$v = new ValueObject();
$v->events()->attach('inject', function($e) {
$values = $e->getParam('values');
if (!$values) {
return;
}
if (!isset($values['date'])) {
$values['date'] = new DateTime('now');
return;
}
$values['date'] = new Datetime($values['date']);
});
$v->inject(array(
'date' => '2011-08-10 15:30:29',
));
]]></programlisting>
</example>
<example xml:id="zend.event-manager.event-manager.examples.short-circuiting">
<info><title>Short Circuiting</title></info>
<para>
One common use case for events is to trigger listeners until either one indicates no
further processing should be done, or until a return value meets specific criteria.
As examples, if an event creates a Response object, it may want execution to stop.
</para>
<programlisting language="php"><![CDATA[
$listener = function($e) {
// do some work
// Stop propagation and return a response
$e->stopPropagation(true);
return $response;
};
]]></programlisting>
<para>
Alternately, we could do the check from the method triggering the event.
</para>
<programlisting language="php"><![CDATA[
class Foo implements Dispatchable
{
// assume composed event manager
public function dispatch(Request $request, Response $response = null)
{
$argv = compact('request', 'response');
$results = $this->events()->triggerUntil(__FUNCTION__, $this, $argv, function($v) {
return ($v instanceof Response);
});
}
}
]]></programlisting>
<para>
Typically, you may want to return a value that stopped execution, or use it some
way. Both <methodname>trigger()</methodname> and
<methodname>triggerUntil()</methodname> return a
<classname>ResponseCollection</classname> instance; call its
<methodname>stopped()</methodname> method to test if execution was stopped, and
<methodname>last()</methodname> method to retrieve the return value from the last
executed listener:
</para>
<programlisting language="php"><![CDATA[
class Foo implements Dispatchable
{
// assume composed event manager
public function dispatch(Request $request, Response $response = null)
{
$argv = compact('request', 'response');
$results = $this->events()->triggerUntil(__FUNCTION__, $this, $argv, function($v) {
return ($v instanceof Response);
});
// Test if execution was halted, and return last result:
if ($results->stopped()) {
return $results->last();
}
// continue...
}
}
]]></programlisting>
</example>
<example xml:id="zend.event-manager.event-manager.examples.priority">
<info><title>Assigning Priority to Listeners</title></info>
<para>
One use case for the <classname>EventManager</classname> is for implementing caching
systems. As such, you often want to check the cache early, and save to it late.
</para>
<para>
The third argument to <methodname>attach()</methodname> is a priority value. The
higher this number, the earlier that listener will execute; the lower it is, the
later it executes. The value defaults to 1, and values will trigger in the order
registered within a given priority.
</para>
<para>
So, to implement a caching system, our method will need to trigger an event at
method start as well as at method end. At method start, we want an event that will
trigger early; at method end, an event should trigger late.
</para>
<para>
Here is the class in which we want caching:
</para>
<programlisting language="php"><![CDATA[
class SomeValueObject
{
// assume it composes an event manager
public function get($id)
{
$params = compact('id');
$results = $this->events()->trigger('get.pre', $this, $params);
// If an event stopped propagation, return the value
if ($results->stopped()) {
return $results->last();
}
// do some work...
$params['__RESULT__'] = $someComputedContent;
$this->events()->trigger('get.post', $this, $params);
}
}
]]></programlisting>
<para>
Now, let's create a <interfacename>ListenerAggregate</interfacename> that can handle
caching for us:
</para>
<programlisting language="php"><![CDATA[
use Zend\Cache\Cache,
Zend\EventManager\EventCollection,
Zend\EventManager\ListenerAggregate;
class CacheListener implements ListenerAggregate
{
protected $cache;
public function __construct(Cache $cache)
{
$this->cache = $cache;
}
public function attach(EventCollection $events)
{
$events->attach('get.pre', array($this, 'load'), 100);
$events->attach('get.post', array($this, 'save'), -100);
}
public function load($e)
{
$id = get_class($e->getTarget()) . '-' . json_encode($e->getParams());
if (false !== ($content = $this->cache->load($id))) {
$e->stopPropagation(true);
return $content;
}
}
public function save($e)
{
$params = $e->getParams();
$content = $params['__RESULT__'];
unset($params['__RESULT__']);
$id = get_class($e->getTarget()) . '-' . json_encode($params);
$this->cache->save($content, $id);
}
}
]]></programlisting>
<para>
We can then attach the aggregate to an instance.
</para>
<programlisting language="php"><![CDATA[
$value = new SomeValueObject();
$cacheListener = new CacheListener($cache);
$value->events()->attachAggregate($cacheListener);
]]></programlisting>
<para>
Now, as we call <methodname>get()</methodname>, if we have a cached entry, it will
be returned immediately; if not, a computed entry will be cached when we complete
the method.
</para>
</example>
</section>
</section>