ok so the breaking in the networking test is because of the changed semantics. This test spawned the client fthread first, then ran the server on the mainline.
The problem is the client did a connect(), and whilst previously the server got started before it ran, now the server would be started afterwards. Connect is asynchronous, however it should fail. The problem is that then the server starts and hangs waiting for a connection that has already failed. So there's actually no bug in the driver code .. the test case needs to be changed to account for the new semantics. And the connection failure should be checked as well. (if it didn't hang forever .. not sure ..) This is a bug in Faio (Felix code). The library code just doesn't bother to check for an error :) -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
