WindowsLDP
WindowsLDP (Load Distribution Program) is a quasi-static gear design and analysis tool for external and internal spur and helical gear pairs. This software program has been adapted and used extensively by most of the consortium members as the main gear design and analysis tool. Variations of this model to perform surface wear and duty cycle analyses are also available. WindowsLDP employs computationally efficient and accurate semi-analytical formulations to compute the load distribution between multiple mating teeth of gears. With the predicted load distribution, it computes the loaded transmission error, root and contact stress distributions, mesh stiffness functions, tooth forces as well as other design relative parameters such as lubricant film thickness and surface temperature. User has the choice of using SI or English units in the analyses. WindowsLDP’s capabilities also include multi-torque analyses and manufacturing robustness analyses.
Learn more
quark
The goal of this project is to do one thing and do it well, namely serving static web directories and doing that right. Most other solutions either are too complex (CGI support, dependencies on external libraries, etc.) or lack features you expect (TLS, virtual hosts, partial content, not modified since, etc.). quark tries to find a midway and just restrict itself to being static while still offering functions you only find in more bloated solutions and being as secure as possible (chroot, privilege dropping, strict parsers, no malloc at runtime, pledge, unveil, etc.). We believe that most of the web does not need to be dynamic and increasing complexity on server-side applications is one of the main reasons for the web obesity crisis. The common approach nowadays is to do everything on the server, including parsing requests, modifying files and databases, generating HTML and all that using unfit languages like PHP or JavaScript, which is a security and efficiency nightmare.
Learn more
Tornado Web Server
Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed. By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado is different from most Python web frameworks. It is not based on WSGI, and it is typically run with only one thread per process. While some support of WSGI is available in the tornado.wsgi module, it is not a focus of development and most applications should be written to use Tornado’s own interfaces (such as tornado.web) directly instead of using WSGI. In general, Tornado code is not thread-safe. Tornado is integrated with the standard library asyncio module and shares the same event loop (by default since Tornado 5.0). In general, libraries designed for use with asyncio can be mixed freely with Tornado.
Learn more
Eclipse Jetty
Jetty provides a web server and servlet container, additionally providing support for HTTP/2, WebSocket, OSGi, JMX, JNDI, JAAS and many other integrations. These components are open source and are freely available for commercial use and distribution. Jetty is used in a wide variety of projects and products, both in development and production. Jetty has long been loved by developers due to its long history of being easily embedded in devices, tools, frameworks, application servers, and modern cloud services. Full-featured and standards-based. Open source and commercially usable, flexible and extensible, small footprint, embeddable, asynchronous, enterprise scalable, and dual-licensed under Apache and Eclipse. Large clusters, such as Facebook Presto. Cloud computing, such as Google AppEngine. With the direction of Java and the JakartaEE project (formerly JavaEE) in 2020, the current recommended version of Jetty for use depends upon the servlet API version, desired licensing, etc.
Learn more