Support multiple connections at once #11

Closed
opened 2022-09-28 09:07:19 +00:00 by heartles · 3 comments
Owner
  • Use regular zig async/await
  • SQL interface needs to be updated to support this
  • Figure out how event loop works (could use std.event.Loop or make our own, if needed)

for postgres:
https://www.postgresql.org/docs/9.5/libpq-async.html

- Use regular zig async/await - SQL interface needs to be updated to support this - Figure out how event loop works (could use std.event.Loop or make our own, if needed) for postgres: https://www.postgresql.org/docs/9.5/libpq-async.html
Author
Owner

async in self-hosted pushed back from zig 0.10.0 😠 https://github.com/ziglang/zig/issues/6025

async in self-hosted pushed back from zig 0.10.0 😠 https://github.com/ziglang/zig/issues/6025
Author
Owner

in the meantime we can still support this using os threads or forkng/ipc. We could also switch to the stage1 compiler, except that it has tighter restrictions on what values can be comptime. maybe we can work around this, but we're also left with the significantly higher compile times of stage1, which impact our metaprogramming-heavy server

in the meantime we can still support this using os threads or forkng/ipc. We could also switch to the stage1 compiler, except that it has tighter restrictions on what values can be comptime. maybe we can work around this, but we're also left with the significantly higher compile times of stage1, which impact our metaprogramming-heavy server
heartles added a new dependency 2022-10-13 09:37:17 +00:00
heartles changed title from Make server asynchronous to Support multiple connections at once 2022-10-13 09:37:36 +00:00
heartles self-assigned this 2022-10-13 09:37:49 +00:00
heartles added a new dependency 2022-10-13 09:40:16 +00:00
heartles added this to the v0.0.2 milestone 2022-10-13 09:40:31 +00:00
heartles added the
backend
label 2022-10-13 10:32:30 +00:00
Author
Owner

closed with cb2f97a28f

closed with cb2f97a28f
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: heartles/fediglam#11
No description provided.