What is the Web application developer framework

What is the Web application developer framework?

// What is an applicationProgramDevelopment Framework

 

 

the ArcGIS web application developer framework (ADF) for the Microsoft. NET framework enables you to integrate GIS data and capabilities into your web applications. the ADF shortdes a set of Web controls, classes, frameworks and APIs that you must l use to build your web applications. to get started, you can use manager, an administrative Web application written with ArcGIS Server and ArcIMS, to step through a comprehensive Web Application Designer to generate a predesigned web site. alternatively, you can start building your web application in Visual Studio with the web mapping application template, which offers basic map display, navigation, and interactive capabilities. you can also use the Web controls directly to create a web site from scratch or develop your own specialized (specified) application in a style that conforms (compliant) to your existing web site.

Translation: Microsoft. the. NET framework allows you to integrate GIS data and GIS functions into your web applications. the. NET Framework includes a series of web spaces, classes, and architectures, and some APIs (application programming interfaces) that allow you to create your own web applications, you can use a network application manager included in the ArcGIS service and ArcIMS service to create a predefined website, alternatively, you can create your own applications using the map application templates in Visual Studio. These Templates include some basic map display navigation and interaction capabilities. You can also use some website tools to directly splice some fragments to create a website, or develop a dedicated application that is consistent with your existing website style.

 

The distrip (Chart) below highlights the primary components and their basic relationships in the Web ADF. there are five distinct sections to consider: Web controls, Web ADF JavaScript library, task framework, common data source API, and Web ADF graphics and core classes. all sections work in conjunction with one another. note that most of the Web ADF components reside solely on the Web server. at runtime some client-side support content, such as web ADF JavaScript libraries, will be loaded by the browser. A set of data sources supported Out-of-the-box by the web ADF are supported for reference, but are not required for the Web ADF to be utilized (available ). depending on the data source, Web ADF JavaScript may be able to take advantage of browser technologies to interact directly with data source content, such as accessing a map image available via a public virtual directory. external data sources supported by the web ADF out-of-the-box are supported in gray at the bottom of the digoal. these data sources are not installed by the web ADF and are only supported ded to show the relationships with Web ADF components. in general, the Web ADF does not require the use of a specific data source. it can be installed and utilized on its own.

The following chart contains some major components and the basic relationship between these components in the webadf. Here there are five different parts to consider: network controls, JavaScript libraries, task frameworks, common data source interfaces, as well as web ADF ing and some core classes. All parts work together. Note: All the Web ADF components exist independently on the Web server. When running, some components supported by the client, such as the Javascript class library, will be loaded on the browser side. Some external data sources that can be supported by WAF are used as references to be added to the application, but these are not necessary for the use of WAF. Based on the data source, the Web ADF script may be able to directly interact with the data source content using the browser technology. External data supported by the web ADF is contained in the gray section at the bottom of the chart. These data sources are not installed by WAF, but are only used to demonstrate the relationship between the data sources and WAF components. Generally, the Web ADF is not required to use a data source in a special format. She can install and use herself

.

A set of assemblies are encoded with the Web ADF which contain tangible components associated with each section. the following dimo-highlights the standard nomenclature (naming system) for Web ADF assemblies (SET) that will be discussed in this help system.

Translation: Some sets attached to the Web ADF contain Visualized components in each chapter. The naming system for these sets highlighted in the following charts will be discussed in the help system.

 

 

Web controls //Network Control

The Web ADF provided des a set of Ajax-enabled web controls built on ASP. net Ajax technologies. the Web controls utilize (used) a set of JavaScript libraries, termed the Web ADF JavaScript Library, to process Asynchronous interaction between browser and web application components as well as remote resources. the Web ADF JavaScript Library provides a public API for Web ADF developers to enhance (extremely high, enhanced) Web applications by leveraging browser capabilities (capability ).

Web ADF includes a series of Web controls based on. NET Ajax technology. Web Components use a series of JavaScript library classes called the Web ADF JavaScript class library to process interactions between browser and web application components and between web and remote resources. The Web javascripte Class Library provides a public API (application interface) for Web ADF developers to Enhance web applications through browser capabilities.

 

Web ADF controls support two Ajax Patterns: the ASP. NET 2.0 callback pattern and the ASP. net Ajax partial PostBack pattern. state between the client browser and the web application on the server is maintained using web ADF callbackresults. callback results can be explicitly created and managed and are designed to processed by web ADF JavaScript to update browser content dynamically.

The Web ADF component supports two types of Ajax models: ASP. NET 2.0 callback function and ASP. NET Ajax partial type. The maintenance of the status between the client browser and the web application on the server depends on the callback result of the Web ADF. Callback results can be created and managed and designed to process dynamic updates of browser content using the Web ADF JavaScript class library.

 

Web ADF JavaScript Library

The Web ADF provided des a public javascript API packaged in a javascript library. the Web ADF JavaScript library is built on the ASP. net Ajax JavaScript library and provides a comprehensive client-side framework which can be used to interact with Web ADF controls and components in a Scriptable environment. web ADF Javascript is designed to enhance web ADF applications by leveraging browser technologies to support client-server synchronization and pure browser interactivity. the library is available for use once a web ADF control resides in the page. it is not designed to be used outside of the Web ADF.

The Web ADF contains a common javascript API, which is encapsulated in a javascript class library. The Web ADF JavaScript class library is based on the ASP. Net jajax JavaScript class library and provides a comprehensive client architecture that can be used to interact with Web ADF controls and components in the ** environment. The Web ADF JavaScript class library is designed to use browser technology to enhance web ADF applications to support clients and browsers **. Once a web ADF control is created on a webpage, this class library can be used. However, this class library cannot be used outside the Web ADF framework.

 

Task framework

the Web ADF task framework is an extensible architecture by which a developer can integrate and deploy custom functionality as "Web tasks" within a Web ADF application. in general, a "Web Task" is a web control that encapsulates a set of related actions to generate results. it is a modular component that can be distributed and "plugged into" Web ADF applications via Visual Studio or the ArcGIS Manager application. the task framework provides the ability to define tively integrate a custom web task into the web ADF and manager. task framework interfaces and classes are encoded in the ESRI. arcGIS. ADF. web. UI. webcontrols. DLL assembly. implementations of the task framework are supported Out-of-the-box with the Web ADF as task controls in the ESRI. arcGIS. ADF. tasks. DLL and ESRI. arcGIS. ADF. arcgisserver. editor. DLL (editortask control only) assemblies.

Web ADFThe task framework is a *** that allows developers to integrate and deploy custom functions similar to network tasks into a web ADF application. Generally, A network task is a network control that triggers a series of interrelated actions to generate a result. An independent component can be added or deployed to the Web ADF application through Visual Studio or ArcGIS management program.The task framework can efficiently integrate a custom web task to the Web ADF and administrator. The task framework interfaces and classes are included in the dynamic link library of ESRI. ArcGIS. ADF. Web. UI. webcontrols.

 

 

Common Data source API

The Web ADF is designed to support data from multiple sources, including ArcGIS Server, ArcIMS, and Microsoft Virtual Earth services. the multi-source architecture allows you to integrate and interact with data from different sources at the same time, in the same application. to accomplish (reach, complete) This, the Web ADF needs a common framework in which data sources can be integrated with Web ADF components. this framework is the common data source API, or in short, the common API.

WAF is designed to support data in multiple data source formats, including ArcGIS Server, ArcIMS, and Microsoft's virtual map service. This multi-data source support allows you to integrate and interact with data from different data sources at the same time and in the same program. To achieve this purpose, the Web ADF requires a public framework in which data sources can be integrated into the web ADF component. This framework is the universal data source API (Application Programming Interface ), or simply put, it is a general API.

 

The common API consists of a set of classes and interfaces in the ESRI. arcGIS. ADF. web. datasources. DLL assembly. these classes and interfaces make up the generic framework that web ADF controls use to interact with different data sources in a common way (thus "common" API ). to utilize a data source as a resource within the web ADF, the data source must provide an implementation of the common API generic framework. the capabilities of the data source will dictate (required) the breadth of implementation. A set of data sources are supported Out-of-the-box including ArcGIS Server, ArcIMS, Microsoft Virtual Earth, arcweb, OGC \ WMS, and Web ADF graphics datasets. each common API implementation (Implementation and fulfillment) is contained within a separate Assembly (Council, set) encoded with the Web ADF.

Public APIs contain a series of classes and interfaces, which are encapsulated in ESRI. ArcGIS. ADF. Web. datasources. dll.

Class Library components. These classes and interfaces enable the Framework class to use a common method to interact with different data sources. In order to use the data source as a resource under the Web ADF, the data source must provide the implementation of a common API framework. The performance of the data source specifies the breadth of its execution. A series of data sources will be supported externally, such as ArcGIS Server, ArcIMS, Microsoft's Virtual Earth, arcweb, OGC \ WMS, and Web ADF graphic dataset. The implementation of each common API is included in an independent set with the Web ADF,

Some data sources are built on (3: built on) an explicit (detailed and clear) programming interface used in the common API implementation (implementation, implementation ). these are known as data source specific (specific) APIs. for example, the common API Implementation of Arc GIS server uses components in the Arc GIS server library ESRI. arcGIS. ADF. arcgisserver. DLL. this library leverages (power, impact) the Arc GIS server soap API to work with Arc GIS server services via a local or internet connection. note, data source specific APIs can be utilized on their own, without web ADF controls or common API implementation classes.

Some data sources are a detailed programming interface used in the implementation of public APIs. These APIs are considered data source-specific APIs. For example, the common API Implementation of ArcGIS Server uses components used in the ArcGIS Server class library. This class library affects ArcGIS soap APIs that work with ArcGIS Server through local or network connections. Note: The APIS specified by the data source can also be used by the user when there is no web ADF control or Universal API implementation class,

 

A set of connection libraries are also encoded with the Web ADF to support local connections to ArcGIS Server and TCP or HTTP connections to ArcIMS.

A series of connected class libraries are also included in the Web ADF, supporting local connection between ArcGIS Server and TCP, and HTTP connection on ArcIMS.

 

 

Web ADF graphics and core classes

Different sources of data can be combined and utilized in a common way (common API) in the Web ADF. as a result, the Web ADF has des a set of components designed to support and enhance working with multiple resources in the Web-tier. most of these components reside in the ESRI. arcGIS. ADF. web. DLL assembly.

Different data sources in the Web ADF framework can be integrated and used in a common way. The result is that the Web ADF contains a series of components that are designed to support or enhance so that they can work with multiple data sources. These components are encapsulated in ESRI. ArcGIS. ADF. Web. dll.

In general, the Web ADF must support some of the basic capabilities of a data source or service. for example, it maintains a graphics dataset, which extends an ADO. net dataset to include spatial properties. the graphics dataset can contain a collection of Web ADF graphics layers which enhance (improved, enhanced) the ADO. net datatable and emulate feature class properties. the Web ADF provided des a set of geometry types, renderers and symbols to manage and display graphic elements in Web ADF graphics layers. since Web ADF graphics capabilities are managed in the Web-tier and an common API implementation is provided, they can be integrated and utilized as map resources. web ADF graphics provide a pure (purely theoretical, complete) Web ADF dataset type to manage selected features, dynamic data, and custom feature data sources.
Generally, the Web ADF must support some basic operations of a data source or service. For example, she maintains a geometric dataset that extends the ADO. Net dataset to contain specific attributes. This graphic dataset can contain a set of set layers. She enhances the ADO. NET data table and imitates the attributes of the element class. Webadf contains a series of geometric types and symbols to manage and display Geometric elements on the Web ADF layer. Because the operations of Web ADF images are managed on Web-tier and a public API is provided, they can be integrated and used as map resources. The Web ADF graph provides a complete Web ADF dataset type to manage selected elements, dynamic data, and custom element data sources.

components of the Web ADF rely on (dependency) The web ADF graphics and core classes to do work and interact with one another. the map control needs to maintain a spatial reference and define display settings for a map resource to generate a map image. A task control may use task results to display graphics on a map with Web ADF graphics layers. A developer may use the generic interfaces of the common API to execute a query using a spatial filter composed of Web ADF geometry. in addition, a set of converter classes are supported in the Web ADF to provide convenient methods for converting between client, Web ADF and Data Source Specific data types. in a true consolidation lidation (enterprise merger, consolidation, enhancement, and Union) environment such as the Web ADF, managing the translation of information between application tiers and source types is essential) to maximizing usability.

The components of the Web ADF depend on those Web ADF graphics and core classes to work and interact with another component. The map control needs to maintain a spatial reference system for a map source and define a display setting to generate a map image.

A task control can display the task result on the map through the webadf layer. A developer may use some common interfaces of common APIs to execute queries containing special filter conditions. In addition, a series of conversion classes are also included in the Web ADF framework, providing conversion methods between customers, Web ADF, and special data sources. In a federated environment, for example, Web ADF, Information Conversion between management applications and data types is essential for maximizing data utilization.