You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a list of feature and target we should aim for a 1.0 release:
portable and Windows support
clustering via GLib.Subprocess and file descriptor sharing
stable server API/ABI
libsoup 3 port
The main issue with fork is portability. While it works great on UNIX, it's not applicable on other platforms. The alternate strategy would be to use spawn (fork + exec with Windows-specific fallback), inherit file descriptors and set the child server to listen to them. Given it being a proper GLib.Subprocess, communication via pipe would be built-in.
The text was updated successfully, but these errors were encountered:
Given the timing of this release, I think we should look into porting VSGI to libsoup 3. There's some interesting benefits including usage of actual GInputStream and GOutputStream APIs which would get write of the Soup.Message wrappers.
Here's a list of feature and target we should aim for a
1.0
release:GLib.Subprocess
and file descriptor sharingThe main issue with
fork
is portability. While it works great on UNIX, it's not applicable on other platforms. The alternate strategy would be to use spawn (fork + exec with Windows-specific fallback), inherit file descriptors and set the child server to listen to them. Given it being a properGLib.Subprocess
, communication via pipe would be built-in.The text was updated successfully, but these errors were encountered: