<feature> Lower-level, non event-based APIs too about wsserver HOT 2 OPEN

I'm not sure this will be applicable here, but when I worked on my Twitch IRC library, I introduced a tick() function which would take care of all the necessary work the library would do during one iteration of the main loop. The user could then write their own main loop (which could include other, arbitrary code) and simply call tick() within that loop. See the wiki on that project in case you want to see if you could potentially draw inspiration from it.

from wsserver.

Hello @domsson,
I don't know if an 'all-in-one' function is ideal for this case... I wanted to leave some things apart like: listening, accepting a connection, receiving frames, and leave the user to invoke them individually.

But you raised an interesting point: the approach I described in the issue was designed to use blocking routines: wait for a connection, wait for frames, and so on. In fact, the entire wsServer was designed this way.

Your approach on the other hand suggests non-blocking routines (and in fact for that you use epoll in your project). It would be interesting if these routines that I suggested could be non-blocking too so that the user could use them either with threads, select, poll, epoll, libevent, etc.

But maybe this requires even major changes in the source code since my routines couldn't block in the midst of a received frame for example, as they do at the moment.

from wsserver.