Sun Wu'kong

1 millisecond == 1000 microsecond Telecom apps often handle hundreds of thousands of concurrent connections while still satisfying soft real-time requirements. But design is key. I'm curious so when I have some time, probably in a month, I'll look into it.

1000 milliseconds == 1 microsecond Telecom apps often handle hundreds of thousands of concurrent connections while still satisfying soft real-time requirements. But design is key. I'm curious so when I have some time, probably in a month, I'll look into it.

Erlang was designed for soft real-time telecom systems - specifically for handling many asynchronous connections at low latency. Of course, designing the server app would have the added complexity of essentially merging these connections into a big group call ...

There are more robust language frameworks built for communication-centric processing, eg Erlang. But that'd mean a redesign of the server...

My little server has been up pretty consistently for a couple of months, now. It's only been down for recompiles and OS updates. The most I've seen is 6 simultaneous users, but the log is unclear if this is really the case, ie. it shows connects but not disconnects.

Just like to throw in my interest in choir rehearsal support -- 4 choirs of 30 to 60 singers, each. I've just started early testing and running into issues with ASIO4ALL configuration (different versions of Windows), finding decent hardware to dedicate to the server, etc.