![]() ![]() ![]() Nevertheless, in today's world, with ASP.NET, PHP, Perl and many other scripting languages providing essentially the same functionality, you may wonder why you would bother creating your own CGI application with C#. Applications on the server communicating in CGI have all the functionality of any other native application, such as database access or reading input files. The Common Gateway Interface, or CGI, is a long standing W3C standard for communicating between a web page and an application available on the web server. Even if you have never worked with threading in C# before, I believe you will not have trouble with that part or any other sections that earned the "Intermediate" status. Threading is presented in its most straight forward of terms, however, and only briefly utilized, so don't fret. Despite that simplicity, I've labeled this as "Intermediate" because in order to take total advantage of CGI, I had to slip in some intermediate things, such as threading. Although this sounds like a lofty goal, CGI is actually quite easy to get into and gains most of its power from its simplicity. ![]() This article will attempt to cover everything you need to know to work with the Common Gateway Interface in C#, including reading the input of POSTs and GETs. How About Your Own Scripting or How to Get Rid of That IIS Script And Executable Security Issue.Fixing the Input Blocking Dilemma for POST.Fixing the Console Input Buffering Dilemma for POST.Using IIS to Launch our App in a Web Page.A Thorough Understanding of the Common Gateway Interface.Why you might not want to use CGI with C#. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |