Download the PHP package homer/yunba-push without Composer
On this page you can find all versions of the php package homer/yunba-push. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download homer/yunba-push
More information about homer/yunba-push
Files in homer/yunba-push
Package yunba-push
Short Description Message pushing implementation with yunba as backend
License proprietary
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 yunba-push
Yunba Push Service
Use Restful APIs exposed by Yunba to implement message pushing service.
This service provides only the most basic features, and designated to be integrated into other project as infrastructure.
API
construct
__construct($appKey, $secretKey, array $options = null, ClientInterface $client = null)
$appKeyapp key (from Yunba portal)$secretKeysecret key (from Yunba portal)$optionssome configurations, including:url(optional)yunba's url, default to 'http://rest.yunba.io:8080'alias_size(optional) maximum #. of aliases in a batch. Yunba suggests that no more than 1000 aliases in a batch is preferred. default to800.
- $client http client
push message to topic
You can push a topic, and those who subscribed that topic will receive the message (it follows the publish/subscribe pattern). You can do that in either asynchrounous or synchrounous manner.
pushToTopic($topic, $message, array $options = [])
pushToTopicAsync($topic, $message, array $options = [])
$topictopic to push message to$messagemessage to push$optionsoptions for Yunba's 'publish' or 'publish_async' method-
return stringmessage idNote: The message given will be pushed as a whole, even if it's an array. Call this method multiple times if you want to push multiple messages. For example,
pushToTopic($topic, ['message1', 'message2'])won't push two messages to the topic, but one message with its content as '["message1","message2"]', which is just a plain JSON string.
push message to alias
This is how Yunba sends uni- and multi-cast messages(while pushing message to topic sends broadcast).
pushToAlias($alias, $message, array $options = [])
$aliasalias to push message to$messagemessage to push$optionsoptions for Yunba's 'publish_to_alias' or 'publish_to_alias_batch' methodreturn string|arraydepending on whether you're pushing message to one or more aliases
check async topic message
Check status of messages that pushed via topic in async manner.
$topicthe topic$messageIdid of the message being checkedreturn stringstatus of the message. Refer to Yunba's doc for detail.
