Well this is a good idea. Since 2006 (well maybe since 2008 when i got s2) i was smart enough to find some leagues for me. But i think there could be very little something more like a league pyramid.
I mean if someone is interested in endurance leagues and then he gets sorted only endurance leagues and then its sorted for example from "top" league through middle to lower ends. That might help someone who wanted to go to the "top" but he doesn't know when to drive first (in which league to begin and gain experience). Also LFS could be better organised in this area.
Just like in real life, you know if you want to be in Formula 1 you have to start from karting then some formula 2000 or F3/GP3 then F2/GP2 or world series by renault and then F1.
At the moment someone in LFS might not have an idea how to get to the "top" leagues or at least what league will suit him and his skills.
Of course it probably isn't main thing for now, but i think it could be very nice and very usefull to have something like that in future.
As someone who's currently implementing WebSockets inside of PHP... It's **** terrible ;p.
ReactPHP is great, which is what most of the "cool" PHP stiff is based off of, but WebSockets as a standard is so retarded in its implementation. Most people implement it in a insane way, which doesn't help, where they wrap their WebApp and WebSocket routes inside this massive "App" object, which I hate, but unfortunately is the way WebSockets is implemented. (As a true upgraded connection from HTTP, and uses the same initial connection as well without option to route to different socket)
Currently, I've resorted to creating a 2nd HTTP server (built in PHP, not a webserver) that's handling WebSocket handshaking + connection management. It's a bloody nightmare to integrate at the core of an application.
I've built websockets into the insim relay - it's the ideal program to do this for and actually quite easy. I only had to detect websocket requests on the usual port and from there on wrap existing packets in websocket frames and vice versa. And done!
But yea, don't you always need some separate service to provide websocket functionality? Nginx or Apache, etc would only serve as proxy, no? I never even understood how that would work, technically ... in my eyes it's easier to just create my own connection handler :P
We don't even have a web server in our stack anymore .
I'll figure it out, it was a bit of a rant because I dislike the upgrade process. I would prefer a separate connection rather than devouring the initial HTTP upgrade request. It's not been fun, especially trying to implement a websocket server that is "compliant" to the RFC.
“This planet has - or rather had - a problem, which was this: most of the people living on it were unhappy for pretty much all of the time. Many solutions were suggested for this problem, but most of these were largely concerned with the movement of small green pieces of paper, which was odd because on the whole it wasn't the small green pieces of paper that were unhappy.”
― Douglas Adams, The Hitchhiker's Guide to the Galaxy