From c5c49e33c69cd90b83375b45e72d283647a7e0e5 Mon Sep 17 00:00:00 2001 From: Khuda Dad Nomani <32505158+KhudaDad414@users.noreply.github.com> Date: Thu, 23 Feb 2023 14:19:28 +0000 Subject: [PATCH] Update docs/functions.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Fran Méndez --- docs/functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/functions.md b/docs/functions.md index bfd2f951e..71585d58e 100644 --- a/docs/functions.md +++ b/docs/functions.md @@ -37,7 +37,7 @@ export default async function (event) { |---|---|---| |send|array<[OutboundMessage](#anatomy-of-an-outbound-message)>|A list of outbound messages to send when the processing of the inbound event has finished. All clients subscribed to the given channel/topic will receive the message. |reply|array<[OutboundMessage](#anatomy-of-an-outbound-message)>|A list of outbound messages to send as a reply when the processing of the inbound event has finished. This is useful when the target of your message is the sender of the inbound event. Note, however, that this only works when you're running Glee as a server. For example, using `reply` when receiving a WebSocket message is fine and the reply will exclusively go to the client that sent the message. However, if you're receiving a message from an MQTT broker, `reply` will work exactly the same way as `send` above, and will send the message to all the clients subscribed to the given channel/topic. -|invoke|array<[InvokeRequest](#anatomy-of-an-invoke-message)>|A list of requests for reaching an HTTP/HTTPS endpoint. This is useful when you have a software as a service (SaaS) function and want it to be treated as one of Glee's functions. +|invoke|array<[InvokeRequest](#anatomy-of-an-invoke-message)>|A list of requests for reaching an HTTP/HTTPS endpoint. This is useful when you have a Serverless function and want it to be treated as one of Glee's functions. ##### Anatomy of an outbound message