Download the PHP package trinity/messages without Composer
On this page you can find all versions of the php package trinity/messages. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package messages
Messages
This bundle provides basic framework for transferring data.
It is based on simple idea: to have a unified process of sending, receiving, packing(serializing) and unpacking(unserializing) data across multiple(or single one) systems.
This bundle is meant to be used for client-server communication. But it is usable in any other form or communication.
The bundle itself does not provide any way of actual "sending" of the messages. It can be therefore used with e.g. rabbitMQ or HTTP.
The bundle defines basic "protocol" for sending the messages by defining all the field that are required.
Each message is "signed" with very basic method. Each sender and receiver has it's id(public key) and secret(secret key).
Each message sent(serialized) has:
- uid - unique identification of the message
- clientId - unique identification of the client which is either sender of this message or which is the message meant to be sent to. It is used on server to choose a private key to check hash of the message.
- jsonData - the data which are sent in the message
- hash - simple hash of the message information and data
- type - type of the message. This field is used while unpacking the message
- parentMessageUid - uid of the message which is this message responding to
- sender - identification of the sender - it can be anything you need. It is meant to be used by the lower level classes which are responsible for actual sending of the message(via rabbitMQ, HTTP, etc.)
- destination - identification of the sender - it can be anything you want. It is meant to be used by the lower level classes which are responsible for actual sending of the message(via rabbitMQ, HTTP, etc.)
- user - identification of the user which made the message. If you need to know who is responsible for the message.
All versions of messages with dependencies
symfony/event-dispatcher Version ~3.0 | ~4.0
symfony/http-kernel Version ~3.0 | ~4.0
symfony/dependency-injection Version ~3.0 | ~4.0
symfony/config Version ~3.0 | ~4.0