• Re: =?UTF-8?Q?=E2=80=9CThe?= end of software secrecy is almost upon

    From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:48:49 2026
    From Newsgroup: alt.folklore.computers

    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able,
    but don't like them.
    It has nothing to do with availability and functionality of select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on sockets.


    By "multiplex on sockets" do you mean supporting more then one connection
    on a single socket? Serious question here: could you tell me how this can
    be useful?

    No I don't mean that and I can't be bother explaining what multiplexing means to someone who's clearly never used it.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:54:20 2026
    From Newsgroup: alt.folklore.computers

    On Mon, 2 Nov 2026 23:46:58 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


    That's nonsense. That part of Winsock2 API did not change since 1993.
    That is, in early 2000s they added poll() (WAASAPoll), but select() is
    the same BSD select() from the very beginning, just a little easier to
    use than original, because nfds is DNC.
    Now, if you woulds say that on Winsock2 select() can't multiplex
    waiting for socket I/O with waiting for other sorts of I/O (files and
    pipes) then your statement would make more sense*.

    Yes, for some bizarre reason MS implemented the userspace sockets as some
    kind of handle instead of an integer file descriptor like every other sockets library.

    2) today, with nearly all file I/O deeply cached, multiplexing waiting
    for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing >sockets with pipes could still make sense, infrequently.

    Depends on the use case.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:54:51 2026
    From Newsgroup: alt.folklore.computers

    On Mon, 2 Nov 2026 14:59:26 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:32 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 31 Oct 2026 05:37:23 -0000 (UTC)
    Lawrence =3D?iso-8859-13?q?D=3DFFOliveiro?=3D <ldo@nz.invalid> gabbled: >>>>> Here=E2=80=99s a fun little thing: if you set a socket to nonblocking and >>>>> then do the connect(2) call, it will seemingly fail with an
    EINPROGRESS error. But in fact, the connection attempt gets
    initiated, and you can monitor its subsequent progress from your
    event loop. =20
    =20
    Far too many devs don't know about or don't understand multiplexing
    using select() or poll(). Admittedly these are borked on Windows as
    you can't use sockets with them=20

    On what planet?

    On this one where you see code that is only multithreaded in order to serve >> individual sockets, not because it needs to be.


    Either you are trolling or don't have a clue?

    Seems to be your standard response to anyone you disagree with. Go back under your bridge.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:22:52 2026
    From Newsgroup: alt.folklore.computers

    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    On Mon, 2 Nov 2026 14:59:26 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:32 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 31 Oct 2026 05:37:23 -0000 (UTC)
    Lawrence =3D?iso-8859-13?q?D=3DFFOliveiro?=3D <ldo@nz.invalid>
    gabbled:
    Here=E2=80=99s a fun little thing: if you set a socket to
    nonblocking and
    then do the connect(2) call, it will seemingly fail with an
    EINPROGRESS error. But in fact, the connection attempt gets
    initiated, and you can monitor its subsequent progress from your
    event loop. =20
    =20
    Far too many devs don't know about or don't understand multiplexing
    using select() or poll(). Admittedly these are borked on Windows as
    you can't use sockets with them=20

    On what planet?

    On this one where you see code that is only multithreaded in order to
    serve
    individual sockets, not because it needs to be.


    Either you are trolling or don't have a clue?

    Seems to be your standard response to anyone you disagree with. Go back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:24:07 2026
    From Newsgroup: alt.folklore.computers

    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    On Mon, 2 Nov 2026 14:59:26 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:32 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 31 Oct 2026 05:37:23 -0000 (UTC)
    Lawrence =3D?iso-8859-13?q?D=3DFFOliveiro?=3D <ldo@nz.invalid>
    gabbled:
    Here=E2=80=99s a fun little thing: if you set a socket to
    nonblocking and
    then do the connect(2) call, it will seemingly fail with an
    EINPROGRESS error. But in fact, the connection attempt gets
    initiated, and you can monitor its subsequent progress from your
    event loop. =20
    =20
    Far too many devs don't know about or don't understand multiplexing
    using select() or poll(). Admittedly these are borked on Windows as
    you can't use sockets with them=20

    On what planet?

    On this one where you see code that is only multithreaded in order to
    serve
    individual sockets, not because it needs to be.


    Either you are trolling or don't have a clue?

    Seems to be your standard response to anyone you disagree with. Go back under
    your bridge.


    Before you listen to this, be sure to not in a mood to get really pissed
    off:

    https://youtu.be/mrKKBBUQnYg

    ;^) too late. Your fate of windows is misguided. It has some fun things.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 11:24:54 2026
    From Newsgroup: alt.folklore.computers

    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to >>>>> serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able, >>>> but don't like them.
    It has nothing to do with availability and functionality of select/poll >>>> on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on sockets.


    By "multiplex on sockets" do you mean supporting more then one connection
    on a single socket? Serious question here: could you tell me how this can >> be useful?

    No I don't mean that and I can't be bother explaining what multiplexing means to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Like, search for "unix select", or something?

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:34:52 2026
    From Newsgroup: alt.folklore.computers

    On 10/27/2026 8:03 AM, Scott Lurndal wrote:
    cross@spitfire.i.gajendra.net (Dan Cross) writes:
    In article <20261027102255.00006052@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Tue, 27 Oct 2026 09:06:26 +0100
    David Brown <david.brown@hesbynett.no> wrote:
    [snip]
    And there are languages like Erlang that divide everything into
    micro-processes, and use the same mechanisms for controlling and
    passing data around regardless of whether this little processes are
    in the same thread, or different threads, different OS processes, or
    different computers. That works because there are very narrow and
    tightly controlled mechanisms for sharing data.

    Note that these are both languages that run on a VM, not compiled
    languages.

    What you wrote about Erlang resembles MPI, which of course is readily
    available for many compiled or jitted languages, including Fortran, C
    and C++.
    I tried to utilize MPI 20 years ago, but the thinking behind it is to
    different from mine, so I ran away in horror.

    Erlang uses the "actor" model to represent concurrency; state is
    held by each actor, and actors communicate via message passing,
    potentially changing state in response to messages. This is a
    model for _concurrency_, in which multiple independent threads
    of execution are coordinated to some in a single system.

    Chorus (the microkernel) worked in a similar fashion. The
    microkernel coordinated between actors using message passing.

    The actors implemented the higher level operating system
    functionality. The Amadeus project, for example, implemented
    a version of unix on top of the microkernel using message
    passing between actors (The Object manager handled files and
    filesystems, the Process actor handled the POSIX process
    and thread (SVR4.2ES/MP threads) interfaces including fork,
    and light-weight processes that implemented threads, and
    the Streams actor provide system V streams support and
    networking.

    Unisys released the OS as part of their massively parallel
    OPUS computer system.

    There are many ways to handle proper sync in multiprocess systems. Indeed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:36:44 2026
    From Newsgroup: alt.folklore.computers

    On 10/26/2026 10:56 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 19:51:23 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 8:39 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 16:58:04 -0700, Chris M. Thomasson wrote:

    Keeping them up to date is, afaict, manual.

    In the Linux world, we have rCLdevelopmentrCY packages versus rCLruntimerCY >>> packages.

    The development package contains the source includes, pkg-config
    info etc. The runtime version includes the actual shared library.
    So your built package has a dependency on the latter; when a user
    tries to install your package, it should automatically pull in the
    latter as necessary.

    Example from my system:

    lrwxrwxrwx 1 root root 13 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so -> libcairo.so.2
    lrwxrwxrwx 1 root root 21 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so.2 -> libcairo.so.2.11804.4
    -rw-r--r-- 1 root root 1366728 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so.2.11804.4

    Where did these come from?

    root@theon:~ # dpkg-query -S /usr/lib/x86_64-linux-gnu/libcairo.so.2 >>> libcairo2:amd64: /usr/lib/x86_64-linux-gnu/libcairo.so.2

    root@theon:~ # dpkg-query -S /usr/lib/x86_64-linux-gnu/libcairo.so
    libcairo2-dev:amd64: /usr/lib/x86_64-linux-gnu/libcairo.so

    Notice how the development library is not versioned, but is just a
    symlink to a versioned library.

    The runtime library is always versioned. This allows multiple
    versions of the library to be present at once, with some older
    packages, that havenrCOt been rebuilt, still depending on an older
    version, while up-to-date packages make use of the newer version.

    I was in the linux world for a whiel, along with solaris, etc. But
    Windows, oh my. vcpkg is a big turn.

    Windows isnrCOt even in the same league, is it.

    Windows is there. :^D
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:38:55 2026
    From Newsgroup: alt.folklore.computers

    On 10/22/2026 12:20 AM, David Brown wrote:
    [...]
    For the particular case of why C++ supports threads but not processes,
    the answer should be obvious.

    Indeed!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:48:17 2026
    From Newsgroup: alt.folklore.computers

    On 10/27/2026 11:36 AM, Scott Lurndal wrote:
    Peter Flass <Peter@Iron-Spring.com> writes:
    On 10/27/26 08:00, James Kuyper wrote:
    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote:
    [restore snippage]>> On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote: >>>>>> On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there. >>>>>>
    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of
    solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each >>>>>> one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous >>> comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..If that isn't your actual opinion of fread(),
    your comments need to be at least a little more nuanced to avoid
    applying to fread().

    The difference is that the size of the buffer for fread() is the maximum
    you want/expect to read. The size of an object is the size it is, not
    necessarily what you expect. If you don't provide enough space you will
    truncate.

    Which isn't a significant issue with fread, since the underlying stdio
    buffer (or kernel file cache or terminal driver buffer) will hold the
    unread information for the next call to fread.

    fread(3) is basically obsolete for most high-performance applications
    which map the file directly into the process address space (mmap).

    Ditto.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 16:22:23 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go back
    under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard Windows approach of chucking threads at everything.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 16:24:03 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to >>>>>> serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able, >>>>> but don't like them.
    It has nothing to do with availability and functionality of select/poll >>>>> on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on >sockets.


    By "multiplex on sockets" do you mean supporting more then one connection >>> on a single socket? Serious question here: could you tell me how this can >>> be useful?

    No I don't mean that and I can't be bother explaining what multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is such an
    arduous task.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 10:56:20 2026
    From Newsgroup: alt.folklore.computers

    On 11/4/2026 8:22 AM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go
    back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard Windows approach of chucking threads at everything.


    Huh? You mean a thread pool, sometimes we can oversubscribe and use
    hardware threads * 2

    I don't think you should mock IOCP. Then you would be mocking AIO, or io_uring.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 19:53:33 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 4 Nov 2026 10:56:20 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 8:22 AM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go
    back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard
    Windows approach of chucking threads at everything.


    Huh? You mean a thread pool, sometimes we can oversubscribe and use
    hardware threads * 2

    I don't care if its a thread ocean, its still threads being used where they're possibly not needed. Obviously depends on load. But if I'm writing a client such as ssh where the only I/O is via stdin and the socket I'm going to multiplex them in select() or poll(), not have 2 seperate threads.

    I don't think you should mock IOCP. Then you would be mocking AIO, or >io_uring.

    I don't give a toss about IOCP, its a windows thing.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gary Scott@garylscott@sbcglobal.net to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 14:17:02 2026
    From Newsgroup: alt.folklore.computers

    On 11/4/2026 1:53 PM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 10:56:20 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 8:22 AM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go
    back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard >>> Windows approach of chucking threads at everything.


    Huh? You mean a thread pool, sometimes we can oversubscribe and use
    hardware threads * 2

    I don't care if its a thread ocean, its still threads being used where they're
    possibly not needed. Obviously depends on load. But if I'm writing a client such as ssh where the only I/O is via stdin and the socket I'm going to multiplex them in select() or poll(), not have 2 seperate threads.

    I don't think you should mock IOCP. Then you would be mocking AIO, or
    io_uring.

    I don't give a toss about IOCP, its a windows thing.
    I sometimes just reserve space in the page file and let the OS lazy write/read.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 23:53:55 2026
    From Newsgroup: alt.folklore.computers

    On 11/4/26 17:24, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote: >>>>
    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in
    order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or >>>>>> able,
    but don't like them.
    It has nothing to do with availability and functionality of
    select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


    By "multiplex on sockets" do you mean supporting more then one
    connection
    on a single socket?-a Serious question here: could you tell me how
    this can
    be useful?

    No I don't mean that and I can't be bother explaining what
    multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is such an arduous task.


    That's fine too, as a hint, no issue there.

    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.

    Let's leave it at that.

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 15:38:55 2026
    From Newsgroup: alt.folklore.computers

    On Wed, 4 Nov 2026 23:53:55 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:
    On 11/4/26 17:24, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe>
    wrote:
    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in
    order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines.
    Or able,
    but don't like them.
    It has nothing to do with availability and functionality of
    select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't
    multiplex on
    sockets.


    By "multiplex on sockets" do you mean supporting more then one
    connection
    on a single socket?a Serious question here: could you tell me
    how this can
    be useful?

    No I don't mean that and I can't be bother explaining what
    multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is
    such an arduous task.


    That's fine too, as a hint, no issue there.

    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.

    Let's leave it at that.

    Jeroen Belleman
    Unless you didn't pay attention yet, boltar is asshole and proud at
    that.
    Or arshole? I'm not sure what is a correct spelling in his area.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 16:39:45 2026
    From Newsgroup: alt.folklore.computers

    On Fri, 6 Nov 2026 15:38:55 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 4 Nov 2026 23:53:55 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:
    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.
    =20
    Let's leave it at that.
    =20
    Jeroen Belleman

    Unless you didn't pay attention yet, boltar is asshole and proud at
    that.
    Or arshole? I'm not sure what is a correct spelling in his area.

    Neither, but don't worry about it. When you've finished your little sucky
    thumb tantrum maybe mummy will pick up all the toys around your pram for you.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 19:22:12 2026
    From Newsgroup: alt.folklore.computers

    On 11/2/2026 11:15 PM, Charlie Gibbs wrote:
    On 2026-11-03, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:

    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: >>>
    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient, >>>>> so I just spun off another thread and moved on to other things.

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.

    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?

    In our environment that should never happen.

    then using the high performance API's is not necessary for your
    "current" use case. But, well, what happens if it does happen?


    The only legitimate
    users are those that are other elements of our software package.
    Any others (or too many seemingly legitimate users) get a rejection
    message, followed by disconnection.



    --- Synchronet 3.22a-Linux NewsLink 1.2