Result for 19C61C89A20998D35BEACAEC929B1D2D738B9FD3

Query result

Key Value
FileName./usr/share/pear/Symfony/Component/EventDispatcher/Event.php
FileSize2711
MD5D42BE878FE52C0E769A767F731764316
SHA-119C61C89A20998D35BEACAEC929B1D2D738B9FD3
SHA-256D4E00FF4856D0F9E1CEAF1304EB7F2A8CBD334FA884847842F04D4156A0AE0D4
SSDEEP48:UKhg8rcOqcyOM8wyy/4+/2St/ttf/CHP9aJPa/2s/e/Ahm/ut/X3J:/5rctHD9VhL6HPEUnGhy/5
TLSHT1FC51DDD955D41E66009B4BBD738A74C4D263B2BF127A344038DE8BB40F1DF184663DE8
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
MD52AD53F19F87D7F82ED960582B601F43C
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
PackageMaintainerFedora Project
PackageNamephp-symfony2-EventDispatcher
PackageRelease1.fc18
PackageVersion2.1.3
SHA-102186CB7B1421430CA395CB454F2893F23537788
SHA-25665D704B093ED5D9D72C90429346554FF6C2DB135A6242FB4A42FD9EA3FFAFF52
Key Value
MD588681F17233A245CAABDA289C96DF4AA
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
PackageMaintainerFedora Project
PackageNamephp-symfony2-EventDispatcher
PackageRelease1.fc18
PackageVersion2.1.3
SHA-176923197FBAC6B87A319341A6E44FD9C511B89F2
SHA-256C2121F289E04FE0FAE9E7F3819E1C80EE2820FF29E34E178609C91B7E45E1AAD
Key Value
MD57153434287BF98B04457DDAD276057FC
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
PackageMaintainerFedora Project
PackageNamephp-symfony2-EventDispatcher
PackageRelease1.fc18
PackageVersion2.1.3
SHA-1BE665D6049950D8FC015E182A392D2193C836E04
SHA-256FD8D5A541EC1972DA78D59075C2CF2FC6BE3D7481396DA4D11AC76EEFAD2E381