PIPE 4 Web Framework
A brief history of PIPE
PIPE was created to be a lightweight alternative to a big framework. It plays nice with other libraries and frameworks, so it can be integrated into a project easily. You are encouraged to customize PIPE by directly modifying its files, so you can fine tune the inner workings to your necessities.
The identify of PIPE is handing the cycle of data. Thus PIPE tries to create a seemless pipe between server and client. A lot of effort is placed on sending data from place A to B, while automating most of the data validation process.
PIPE 1-3 were never released, PIPE 3.1 preview was released to students, and PIPE 3.1 was used to built a company's ERP system. PIPE 3.1 struggled a lot, of course, being the first time it was put to production. A lot was learned, but it mostly proved to be a good idea in the right direction, but not fully realized. From that learning experience, an update, PIPE 3.2 was planned, but the decision to make a radical re-write is how we ended up with PIPE 4.
PIPE 4 brings radical changes to the most fundamental parts of the framework. The Printer has been audited, the Endpoint system was reworked, and the data system was rebuilt from the ground up.