From 6ce8272b457c26336aa9b1047d529e70b2d3266f Mon Sep 17 00:00:00 2001 From: Josh Berdine Date: Wed, 27 Nov 2024 15:09:30 +0000 Subject: [PATCH] moved source TODO to issue https://github.com/SkipLabs/skip/issues/554 --- www/docs/externals.md | 1 - 1 file changed, 1 deletion(-) diff --git a/www/docs/externals.md b/www/docs/externals.md index 3d6364a3a..18e80f903 100644 --- a/www/docs/externals.md +++ b/www/docs/externals.md @@ -110,4 +110,3 @@ If more control is required or your external system does not fit this form, then For example, your service can keep track of open resources and combine requests to the external service if it supports batched requests, reducing request load and potentially allowing more optimized execution in the non-reactive system. Similarly, an external relational database may support some limited form of reactivity/listening, such as PostgreSQL's `pg_notify`; in that case, a custom Skip `ExteralService` can interpret those updates into a form suitable for use within the Skip framework. -TODO: work out some examples here?