Result for 3FC4664C06C0CF815C67C604D083D14F93ED421B

Query result

Key Value
FileName./usr/share/tests/pear/EventDispatcher/Symfony/Component/EventDispatcher/phpunit.xml.dist
FileSize886
MD5EEBF2E13EA5E23FB7583E3D7B60351F9
SHA-13FC4664C06C0CF815C67C604D083D14F93ED421B
SHA-2564BE7957B6163D5E741FC5140527D4D9B6A200AB1C29058BB37319F2ECB226061
SSDEEP24:2daMo6vBdAOdO6d1Ju9KBt+xttZFYLmU+nZO+yZs+xsZs+1ZsAg:cHCOJhEB7TYL+ctsxav
TLSHT147112420A1FC1AD305D703453B14902A5BE092E7800E117FB39EA3C0AF29E02C2CFD53
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5D2E9D1882573DCF9F4B5890E87D58EC0
PackageArchnoarch
PackageDescriptionThe Symfony2 Event Dispatcher component implements the Observer (http://en.wikipedia.org/wiki/Observer_pattern) pattern in a simple and effective way to make all these things possible and to make your projects truly extensible. Take a simple example from the Symfony2 HttpKernel component. Once a Response object has been created, it may be useful to allow other elements in the system to modify it (e.g. add some cache headers) before it's actually used. To make this possible, the Symfony2 kernel throws an event - kernel.response. Here's how it works: * A listener (PHP object) tells a central dispatcher object that it wants to listen to the kernel.response event; * At some point, the Symfony2 kernel tells the dispatcher object to dispatch the kernel.response event, passing with it an Event object that has access to the Response object; * The dispatcher notifies (i.e. calls a method on) all listeners of the kernel.response event, allowing each of them to make modifications to the Response object. Optional dependency: HttpKernel (php-symfony2-HttpKernel)
PackageMaintainerFedora Project
PackageNamephp-symfony2-EventDispatcher
PackageRelease1.fc19
PackageVersion2.2.1
SHA-11858ABF57FBEE44142FDCF34F63A7EC8E58434FB
SHA-2565C29E4864E16D413BA5FDDF199DB53035DD942E87E4CADE8EE04873C66DAF81D
Key Value
MD59229F7548F4D218C208FFF79E39DE6E1
PackageArchnoarch
PackageDescriptionThe Symfony2 Event Dispatcher component implements the Observer (http://en.wikipedia.org/wiki/Observer_pattern) pattern in a simple and effective way to make all these things possible and to make your projects truly extensible. Take a simple example from the Symfony2 HttpKernel component. Once a Response object has been created, it may be useful to allow other elements in the system to modify it (e.g. add some cache headers) before it's actually used. To make this possible, the Symfony2 kernel throws an event - kernel.response. Here's how it works: * A listener (PHP object) tells a central dispatcher object that it wants to listen to the kernel.response event; * At some point, the Symfony2 kernel tells the dispatcher object to dispatch the kernel.response event, passing with it an Event object that has access to the Response object; * The dispatcher notifies (i.e. calls a method on) all listeners of the kernel.response event, allowing each of them to make modifications to the Response object. Optional dependency: HttpKernel (php-symfony2-HttpKernel)
PackageMaintainerFedora Project
PackageNamephp-symfony2-EventDispatcher
PackageRelease1.fc19
PackageVersion2.2.1
SHA-1B33A3D0A5CDA81C7C7AD5125805FF0BCDA28D9B0
SHA-2564156F31F4FC2E71FF7B5CB9EE8D2EE17DF3538372366868DC5D4E6B91E4CD264
Key Value
MD5CF6453ACBCCA206F986121818F19DF9E
PackageArchnoarch
PackageDescriptionThe Symfony2 Event Dispatcher component implements the Observer (http://en.wikipedia.org/wiki/Observer_pattern) pattern in a simple and effective way to make all these things possible and to make your projects truly extensible. Take a simple example from the Symfony2 HttpKernel component. Once a Response object has been created, it may be useful to allow other elements in the system to modify it (e.g. add some cache headers) before it's actually used. To make this possible, the Symfony2 kernel throws an event - kernel.response. Here's how it works: * A listener (PHP object) tells a central dispatcher object that it wants to listen to the kernel.response event; * At some point, the Symfony2 kernel tells the dispatcher object to dispatch the kernel.response event, passing with it an Event object that has access to the Response object; * The dispatcher notifies (i.e. calls a method on) all listeners of the kernel.response event, allowing each of them to make modifications to the Response object. Optional dependency: HttpKernel (php-symfony2-HttpKernel)
PackageMaintainerFedora Project
PackageNamephp-symfony2-EventDispatcher
PackageRelease1.fc19
PackageVersion2.2.1
SHA-1766AE7E8A1D769D8E44F5F3908EF5C76A5DC2B88
SHA-2563E56C76D666A0553B70C0E17A062DF5FD95B9C8E599119F87ED6E66725A75AC7