<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<p style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Hello,</p>
<p style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">I wanted to reach out and get some feedback from everyone because my company started a project using FS as base several weeks ago, our goal was to optimize and integrate FS more directly into
Windows environments. Here is my question, we would like to share our changes and where should we host our project? Because we understand our build breaks compatibility with the UNIX environments and fails to meet the objectives cross platform compatibility,
however it could contribute greatly and be beneficial to other windows users.</p>
<p style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Here are some of the changes we have made:</p>
<ul style="list-style-type: disc">
<li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">We converted FS core to C++ and having it compiling to .NET 4.0 CLI
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">FS now runs inside its own namespace
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">We replace FS_CLI with a PowerShell shell app
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Supports SQL Server support via the Native SQL Server Client API
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Support for windows clustering (up to 32 node active/active cluster)
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Ties more directly into the Win32 API and has less reliance on open source Libs
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Replaces OpenSSL sockets with Windows encrypted sockets
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Added windows performance monitoring
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">No longer need to use mod_managed for managed modules
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Memory management relies on .Net garbage collection
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Added support for Microsoft Speech
</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">VoiceXML 3.0 and SCXML support</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">No longer supports JS, LUA, PHP development - Modules can be only developed in .NET, C or C++( we feel support for other languages can be added back in but falls outside the scope of our objectives
at this time, support for SCXML should make limit the need for other scripting languages)</li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">Fixed RTP clock timing issues in virtualized environments </li><li style="margin: 0.0px 0.0px 10.0px 0.0px; font: 11.0px Calibri">New configuration file format using .Net App Configuration files (kind of looks like an IIS config file)
</li></ul>
</body>
</html>