WebWriter: A browser-based editor for constructing Web applications

A Novel Approach to HTML Page Creation Using Neural Network

The Internet and World Wide Web (WWW) are now evolving as an important communication technology and a major information resource provider for industry. This paper discusses the development and implementation of a knowledge-based gear design and manufacturing system over the Internet to create new integrated design and manufacturing environments. By providing access to an interactive web-based support system, any designer with a WWW browser becomes a potential user of this on-line design system. Once connected, the designer follows the system instructions and submits the necessary input data on the appropriate web pages. The server receives a request from a client and invokes a CGI (Common Gateway Interface) program that processes the information provided through the user Interface. The CGI parses the data and has the ability to remotely run the knowledge-based gear design system that integrates knowledge about all aspects of gear design and manufacturing and provides powerful reasoning and decision-making capabilities for reducing the time between gear tooth creation, detailed design and manufacturing process specification via the Internet. When the execution is completed, full specifications definition, geometry, kinematic-loads and stresses are determined through Finite Element Analysis (FEA) within ANSYS, VRML models of the gear pair and gearbox assembly including gears, shafts, bearings and housing are exported according to the designer requests and sent back to designer on the web browser. To accomplish this, a combination of HTML, JavaScript, VRML, CGI Script and C++ is used. Finally, an example on spur gear design utilizing a parallel gearbox design model configuration is discussed.

Client-server programming is emerging as an important programming paradigm. Especially important, because of the pervasiveness of the HTTP protocol, is the stateless client-server paradigm, used in the so-called ‘Common Gateway Interface’, or CGI. CGI Programmers must deal with a number of design considerations that are not normally important in conventional programs. The most important are persistence and control of concurrent access. We describe these and other CGI programming considerations, and present a new ‘little’ programming language that was designed specifically as a server-side programming language. © 1998 John Wiley & Sons, Ltd.

HyperSQL is an interoperability layer that enables database administrators to rapidly construct browser-based query interfaces to remote Sybase databases. Current browsers (i.e., Netscape, Mosaic, Internet Explorer) do not easily interoperate with databases without extensive CGI (Common Gateway Interface) programming. HyperSQL can be used to create forms and hypertext-based database interfaces for non-computer experts (e.g., scientists, business users). Such interfaces permit the user to query databases by filling out query forms selected from menus. No knowledge of SQL is required because the interface automatically composes SQL from user input. Database results are automatically formatted as graphics and hypertext, including clickable links which can issue additional queries for browsing through related data, bring up other Web pages, or access remote search engines. Query interfaces are constructed by inserting a small set of HyperSQL descriptors and HTML formatting into text files. No compilation is necessary because commands are interpreted and carried out by the special gateway, positioned between the remote databases and the Web browser. Feedback from developers who have used the initial release of HyperSQL has been encouraging. At present, query interfaces have been successfully implemented for three major NSF-sponsored biological databases: Microbial Germplasm Database, Mycological Types Collection, and Vascular Plants Types Collection.

Chapter 1 - Introduction

With conventional regression test tools for Web applications, it is difficult to specify the values to be verified that are repeated output inside loop statements. We need to select each of these values displayed in Web pages with the mouse. This paper presents a method that automates regression testing of Web applications on the server side. This method makes it easy to specify values to be verified and enables us to specify them when we develop Web applications. We can directly check the verification results on the Web pages that are shown in the Web browser. If we find a fault, we can even directly modify a part of the server program in the Web browser that corresponds to the currently displayed Web page.

Active pages: Intelligent nodes on the World Wide Web

Chapter 6 - Interacting with the user using ASP.NET forms

The Common Gateway Interface (CGI) was the first attempt to enable the creation of dynamic HTML pages which represent a very suitable concept to meet the requirements of web-based applications for remote data analysis (RDA). CGI scripts are still popular, but by now there are new approaches which should be able to solve the main CGI problems. In this paper, we present the most promising one: Java Servlets. We will discuss the advantages and drawbacks of Java Servlets compared to CGI scripts. Moreover, we will do some performance measurements on the basis of simple classification problems and introduce the key functions of the Java Servlet API.

We present an approach to write web applications in the programming languages Haskell [8] and Curry [6]. The web applications we propose are directly based on the Hypertext Transfer Protocol (HTTP) – no additional protocol on top of HTTP is necessary. Although the main ideas are not new and already applied using other programming languages, we believe that features present in modern declarative languages – especially algebraic datatypes – serve well to represent resources on the web. 1 TRANSFER OF RESOURCE REPRESENTATIONS A resource is any piece of information named by a Uniform Resource Identifier (URI). A web application provides access to internally stored information over the Internet or accesses such information provided by other web applications. Usually, (a representation of) this information is transferred using the Hypertext Transfer Protocol (HTTP) [3] – possibly employing some protocol on top of it. Note that we do not primarily consider applications running inside a web browser like [4, 7, 9]. HTTP provides different methods to access resources from which the most important are the GET and the POST method. GET is used to retrieve some information, e.g., web browsers use GET to ask for the content of web pages. POST is used to send information to be processed by a server, e.g., entries in a web form can be sent to the server using POST. While processing the request, the server can update its internally stored information and usually sends back a result of this process. Web applications differ in their use of these two HTTP methods: RPC-style web applications are accessible through a single URI and communication is performed using the POST method. A representation of a procedure call is transferred to the server, which returns a representation of the result of this call as answer to the POST request. Note that both retrieval and update operations are performed using the POST method in RPC-style web applications and the interface of such applications is determined by the procedure calls that are understood by the server. Fielding [2] proposes another architectural style for web applications: He proposes to use the POST method only to update the internal state of the server and to use the GET method to purely retrieve information. Consequently, everything that should be available for retrieval by clients needs to be identified by an own URI. This is a big difference to RPC-style web applications that are usually accessible ?This work was partially supported by the German Research Council (DFG) grant Ha 2457/5-1. through a single URI. In the architectural style proposed by Fielding, a client sends an HTTP GET request to an URI to retrieve a representation of the resource identified by this URI corresponding to the current state of the server. To change this state, the client sends a POST request to the URI of the resource he wants to update. Fielding calls this architectural style Representational State Transfer (REST). The interface of a RESTful web application is given by the methods of HTTP and the URIs identifying the applications resources. In this work, we show how the interface given by the most important HTTP methods can be made available to Haskell or Curry programmers, hiding the details of HTTP communication.

We began this book by discussing general issues surrounding Web application development. The first three chapters introduced the creation of Web applications and Web pages in Visual Studio.NET and prepared you for the detailed information in the chapters that followed. At that stage, we wanted to provide a sufficient informational framework for you to understand and work with the controls made available by ASP.NET, as well as the controls that you would develop yourself. The same framework supported the introduction of ADO.NET and XML Web services, which supply external information to Web applications.

Software testing is indispensable to assure software quality. Traditional software testing techniques are insufficient for modern web applications due to their unique characteristics, such as highly dynamic generation of web pages and interactions with DOM elements. Meanwhile, existing web testing techniques are cumbersome to use in long-term maintenance and evolution because the tests are often brittle in the presence of fast changes to web pages. In this paper, we propose an automatic test generation technique for dynamic web applications. Our technique effectively decouples test code from web pages by automatically generating page objects. Based on page objects, our technique performs iterative feedback directed random test generation. Our evaluation on seven real-world web applications demonstrates that the proposed technique achieves reasonable code coverage (from 23.3% to 90.8%) and can effectively explore dynamically generated web pages (around 14.7 times more than the original static web pages), revealing hundreds of HTML issues and five real errors in the applications.

Java is a relatively new programming language that has been used to develop a World Wide Web-based tool for estimating magnetic resonance (MR) imaging relaxation times, thereby demonstrating how Java may be used for Web-based radiology applications beyond improving the user interface of teaching files. A standard processing algorithm coded with Java is downloaded along with the hypertext markup language (HTML) document. The user (client) selects the desired pulse sequence and inputs data obtained from a region of interest on the MR images. The algorithm is used to modify selected MR imaging parameters in an equation that models the phenomenon being evaluated. MR imaging relaxation times are estimated, and confidence intervals and a P value expressing the accuracy of the final results are calculated. Design features such as simplicity, object-oriented programming, and security restrictions allow Java to expand the capabilities of HTML by offering a more versatile user interface that includes dynamic annotations and graphics. Java also allows the client to perform more sophisticated information processing and computation than is usually associated with Web applications. Java is likely to become a standard programming option, and the development of stand-alone Java applications may become more common as Java is integrated into future versions of computer operating systems.

HTML (HyperText Markup Language), the language of the web, is no longer the only language of the web. But it still is the primary language in which source code of webpages is shared. Originally, HTML pages were always static: the only HTML source of a web page was that was downloaded from a website. Nowadays, much HTML the is visualized in your web browser, is generated on the fly with JavaScript.

A relevant consequence of the expansion of the web and e-commerce is the growth of the demand of new web sites and web applications. As a result, web sites and applications are usually developed without a formalized process, and web pages are directly coded in an incremental way, where new pages are obtained by duplicating existing ones. Duplicated web pages, having the same structure and just differing for the data they include, can be considered as clones. The identification of clones may reduce the effort devoted to test, maintain and evolve web sites and applications. Moreover, clone detection among different web sites aims to detect cases of possible plagiarism. In this paper we propose an approach. based on similarity metrics, to detect duplicated pages in web sites and applications, implemented with HTML language and ASP technology. The proposed approach has been assessed by analyzing several web sites and Web applications. The obtained results are reported in the paper with respect to some case studies.