You can publish messages to listening subscribers via publish: message. Note: Make sure there are at least a few ticks between opening a subscription and closing it, otherwise strange behavior will occur. The channels you subscribe to support wildcard (*) matchers and other patterns, defined by the redis docs: □ When you subscribe to a channel, matching messages sent to the channel will trigger the Event: redis pubsub message event.Ĭonnections that are subscribed to channels get tied up listening for messages and are unavailable to run redis commands. This allows you to listen to published messages to redis from any source, including other servers. This command supports subscribing to pub/sub redis channels. When running commands, make sure to escape unpredictable values such as player input.Īlternatively, include the main redis command as the 'command' input and further arguments as a ListTag input for 'args'. It is normally advised to run commands as ~waitable (see Language: ~waitable), but because of the usual fast responses when the server is on localhost, you can also run commands without ~waiting. If you run redis locally, you can expect responses to take under a millisecond. The redis server runs in memory, meaning requests are insanely fast. Redis is a simple key/value data store that is typically used for caching and sending data between servers. It can run any standard redis commands as well as subscribe for pub/sub redis channel notifications. This command is used to interact with a redis server. Learn about how commands work in The Beginner's Guide. Commands are always written with a '-' before them, and are the core component of any script, the primary way to cause things to happen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |