Libraries tagged by event subscriber

Allows to publish messages and getting response from each subscriber

Go to Download

Will allow you to define anonymous function as event listener callbacks for Shopware (4.2.0+)

Go to Download

Symfony bundle to add the domain event dispatcher (singleton)

Go to Download

Dispatch or defer domain events from a singleton. Handy if you're using DDD and need a singleton domain dispatcher for models.

Go to Download

Simple publish-subscribe library with ability to specify priority for subscribers

Go to Download

A PHP library to implement the observer pattern

Go to Download

An event dispatcher

Go to Download

PimcoreDevkitBundle bundle to generate, bundles, controllers, event subscribers, areabricks ...

Go to Download

A module for the PinkCrab Perique Framework which makes it easy to add subscribers which are triggered during various events within a plugins life cycle(Activation, Deactivation, Uninstall, Update etc).

Go to Download

Wrapper for laravel events so that an event can be published without using a listener and a subscriber command

Go to Download

Publish and subscribe to events in Silverstripe CMS or your Silverstripe application

Go to Download

PHP Service Bus (publish-subscribe pattern)

Go to Download

A simple observer pattern implementation based on symfony event handler, allowing you to subscribe and listen for various events that occur within your application.

Go to Download

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download

A simple implementation of Pub/Sub for PHP

Go to Download