Short URL: http://fsmsh.com/3346
These are exciting times for Falcon’s language development. New and interesting features are being implemented, tested and rolled out at break neck speeds! Not only are core language features being released, but so are a multitude of feathers (Falcon libraries/modules). One such module release is V1.0 Web Oriented Programming Interface (WOPI). It is the intent of this article to cover the basic features/functionalities of WOPI through common web oriented functional examples.
WOPI is an abstraction layer between a web server and the falcon scripts that serves up a web page. At a very high level I like to think of it as the ODBC of web servers.
At a very high level I like to think of WOPI as the ODBC of web servers
By using WOPI, users can easily move their own web based applications to all the supported Front Ends. Front Ends are the plug-in code required to support particular web architecture. The list is quickly growing, but these currently include: Common Gateway Interface (CGI), Fast-CGI, CGI Falcon-Module, Apache 2, and the micro Falcon based web server. WOPI also delivers standardized functionality common to most web based applications such as: HTTP GET & POST Field parsing, Cookie control, Upload control, Simplified output encoding control, template management, session management, persistent data and application-wide data support. The list of basic functionality, as with the Front Ends is also rapidly growing.
Before diving right in here are a few items to get you started if you don’t already have Falcon/WOPI. You can get a [copy of Falcon] (http://www.falconpl.org/index.ftd?page_id=official_download) You can also get a copy of WOPI and the WOPI Documentation
Now that you have all the tools (Falcon and WOPI) let’s get down to it!
Getting startedGo there Read More...