Can I use CGI scripts or executables written in languages other than G (perl, tcl, shell scripts, compiled code, etc) to process client requests?
No, not unless you come up with a modification to the Server code to allow this. The problem here involves argument-passing. LabVIEW and the G Server do not have a convenient way to pass the query string from a client’s browser to any CGI routine other than those written in G. There is also no convenient way to access the result of the non-LabVIEW script and pass it back to the client. Similar limitations are encountered when using the System Exec VI in LabVIEW. • Can other HTTP servers (httpd, etc) make use of CGI routines written in G? How about compiled CGI VIs? No, for reasons similar to those in the above explanation. Native CGI VIs would be completely unusable by other servers, and even with compiled version there is the problem of argument-passing. • Can I embed the HTTP G Server inside an executable and run it on a machine that does not have LabVIEW installed? Yes. In fact, as of LabVIEW 5.1, you do not actually need the Internet Developers Toolkit in order to serve Application
Related Questions
- Can the G Web Server use CGI scripts or executables written in languages other than LabVIEW (Perl, TCL, shell scripts, compiled code, and so on) to process client requests?
- Can I use CGI scripts or executables written in languages other than G (perl, tcl, shell scripts, compiled code, etc) to process client requests?
- Are compiled languages such as C safer than interpreted languages like Perl and shell scripts?
