Sunday, 11 March 2012

History

As the architecture of the World Wide Web was not inherently dynamic, aboriginal hypertext consisted of hand-coded HTML that was appear on web servers. Any modifications to appear pages bare to be performed by the pages' author. To accommodate a activating web folio that reflected user inputs, the Accepted Gateway Interface (CGI) accepted was alien for interfacing alien applications with web servers.2 CGI could abnormally affect server load, though, back anniversary appeal had to alpha a abstracted process.

Programmers capital tighter affiliation with the web server to accredit aerial cartage web applications. The Apache HTTP Server, for example, supports modules that can extend the web server with approximate cipher executions (such as mod perl) or advanced specific requests to a web server that can handle activating agreeable (such as mod jk). Some web servers (such as Apache Tomcat) were accurately advised to handle activating agreeable by active cipher accounting in some languages, such as Java.

Around the aforementioned time, fresh languages were actuality developed accurately for use in the web, such as ColdFusion, PHP and Active Server Pages.

While the all-inclusive majority of languages accessible to programmers to use in creating activating web pages accept libraries to advice with accepted tasks, web applications generally crave specific libraries that are advantageous in web applications, such as creating HTML (for example, JavaServer Faces).

Eventually, mature, "full stack" frameworks appeared, that generally aggregate assorted libraries advantageous for web development into a distinct adamantcomputer application assemblage for web developers to use. Examples of this accommodate ASP.NET, JavaEE (Servlets), WebObjects, web2py, OpenACS, Catalyst, Mojolicious, Ruby on Rails, Django, Zend Framework and Symfony.

No comments:

Post a Comment