As long as no official release gets done, how about addressing some bugs in the meantime?
Given the latest developments in making it easy to create web applications with Java-based web servers like Tomcat [1] using the script taglib [2], it would be great to allow users to supply [oo]Rexx code to run on the web server and get the results back on the client via HTML (the Rexx SAY-instructions executed on the web server would automagically create the HTML-text to be returned to the requesting client). Of course, it would be necessary to make sure that malicious code does not do any harm on the web server, which would be possible having such code run under the supervision of the ooRexx security manager on the web server. In order to be really secure it would be necessary to address the security related bugs in [3]. ---rony P.S.: Also, there is an idea for creating the ability to run script code besides JavaScript on web browsers on the client side, such that one could achieve with ooRexx what was possible on the MS Internet Explorer with ooRexx 3.x, being a Windows script engine, yet, on any operating system. At the moment this is not around the corner, but something I would like to push in another project next year. Then, it would be important to be able to use the ooRexx security manager (like on the MS Internet Explorer) to have those script execute safely on the client. This way one could use a browser for the GUI and for printing for ooRexx programs. [1] Tomcat: <https://tomcat.apache.org/> [2] Script language Taglib with ooRexx demonstration web application (zip and war): <https://sourceforge.net/projects/bsf4oorexx/files/Sandbox/rgf/taglibs/beta/> [3] ooRexx security manager related bugs: <https://sourceforge.net/p/oorexx/bugs/search/?q=security> _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
