Support running from a socket again in sassserver

 A sassserver can run the same when forked or spawned from a
local service, that's the point of textclient. Most sassservers
don't need local service support in any way, and cutting the
support from that saves pulling a good amount of code, but some
do. Put back local service support while refactoring the code
so running as a child from the client (common case) doesn't pull
the socket code.

1 files changed, 24 insertions, 0 deletions

diff --git a/src/libunixonacid/sassserver-internal.h b/src/libunixonacid/sassserver-internal.h
new file mode 100644
index 0000000..71f8a38
--- /dev/null
+++ b/src/libunixonacid/sassserver-internal.h
@@ -0,0 +1,24 @@
+/* ISC license. */
+
+#ifndef SKALIBS_SASSSERVER_INTERNAL_H
+#define SKALIBS_SASSSERVER_INTERNAL_H
+
+#include <stdint.h>
+
+#include <skalibs/functypes.h>
+#include <skalibs/tai.h>
+#include <skalibs/sassserver.h>
+
+typedef struct sassserver_query_s sassserver_query, sassserver_query_ref ;
+struct sassserver_query_s
+{
+  uint32_t id ;
+  tain deadline ;
+  void *data ;
+} ;
+
+#define SASSSERVER_QUERY(a, i) GENSETDYN_P(sassserver_query, &(a)->queries, i)
+
+extern void sassserver_init_structures (sassserver *a, sassserver_send_func_ref, sassserver_cancel_func_ref, size_t, free_func_ref, void *) ;
+
+#endif