Abstract: A concept for providing hierarchical navigation information relative to one or more databases within a distributed computer system is described. In one aspect, this includes a process for hierarchically organizing bodies of information that includes: receiving a query from a user, abstracting a list of descriptors from one or more sources of information selected based on the query, organizing the list according to an hierarchy of nodes referenced in the one or more sources of information and providing information configured to facilitate displaying a graphical user interface illustrating the hierarchy and having user programmable server control classes for accession of nodes in the hierarchy.

Abstract: The described systems and methods are directed at defining web content navigation. The disclosed technique enables the development of web content for a scenario without having to create every navigational control that is needed to manage the flow through the web content in the scenario or to write non-declarative server-side logic to control navigation. This method determines a declaration in a source file for a web page. The declaration is associated with an object. The method determines the views associated with the object where each of the views includes a user-interface. A flow for navigating through the views is determined. The views are rendered in accordance with the navigational flow.

Abstract: In a distributed computing system containing multiple entities such as servers and clients, an object passed between the entities is attached with metadata identifying the type of the object and/or types and values of properties associated with the object. Before the object is passed to an entity in the distributed computing system, the object may be serialized into a data format that the receiving entity can understand.

Abstract: The present invention extends to methods, systems, and computer program products for creating Web forms with automatically generated links. A database mapping for a database is accessed. One or more dynamic queries for querying a database are automatically formulated. The dynamic queries are included in an automatically generated Web site for the database in accordance with the database mapping. User-selected links are also included for executed the dynamic queries. Selection of a link causes a corresponding dynamic query to execute. Relationships between tables in a database can be inferred even when a relationship is not expressly described in schema describing the database. Dynamic queries can be any of sorting, pagination, addition, deletion, and modification queries.

Abstract: A concept for providing a process for parsing at least one code object comprising determining when a page associated with the at least one code object has been previously processed; parsing the page when the page is determined not to have been previously processed; and evaluating a value for a compilation attribute for the page, is described.

Abstract: A server system in typical operation has a process manager, multiple listeners (each to receive requests for its protocols) and multiple worker processes that are each able to handle requests in multiple protocols. At server start-up, each listener connects with the process manager via a pipe published by the process manager. The listener then receives information via the process manager that includes information defining the application(s) for which that listener is to “listen” and associating application(s) to application pool(s). When the listener receives a request for such an application, the listener starts a queue for the associated application pool. The listener may use a hierarchical matching scheme to determine the associated application or application pool from the requested application. The process manager launches an appropriate worker process to handle requests in the listener's protocol. The worker process then makes a connection with the listener.

Abstract: A server system has a process manager, listeners and worker processes in which the listeners connect to worker processes. At server start-up, each listener connects with the process manager via a pipe published by the process manager. The process manager then provides information to each listener associating applications to application pools, and applications for which the listener is to “listen”. When the listener receives a request for which it is to listen, the listener starts a queue for the application or associated application pool. The process manager launches an appropriate worker process to handle requests in the listener's protocol. The worker process then makes a connection with the listener.

Abstract: A server system in typical operation has a process manager, multiple listeners (each to receive requests for its protocols) and multiple worker processes that are each able to handle requests in multiple protocols. At server start-up, each listener connects with the process manager via a pipe published by the process manager. The listener then receives information via the process manager that includes information defining the applications(s) for which that listener is to “listen” and associating selected application(s) to application pool(s). When the listener detects a request for such an application, the listener starts a queue for the associated application pool. In response, the process manager launches an appropriate worker process to handle requests in the listener's protocol. The worker process then makes a connection with the listener.

Abstract: A server system in typical operation has a process manager, multiple listeners (each to receive requests for its protocols) and multiple worker processes that are each able to handle requests in multiple protocols. At server start-up, each listener connects with the process manager via a pipe published by the process manager. The listener then receives information via the process manager that includes information defining the application(s) for which that listener is to “listen” and associating application(s) to application pool(s). When the listener receives a request for such an application, the listener starts a queue for the associated application pool. The listener may use a hierarchical matching scheme to determine the associated application or application pool from the requested application. The process manager launches an appropriate worker process to handle requests in the listener's protocol. The worker process then makes a connection with the listener.

Abstract: The present invention extends to methods, systems, and computer program products for creating Web forms with automatically generated links. A database mapping for a database is accessed. One or more dynamic queries for querying a database are automatically formulated. The dynamic queries are included in an automatically generated Web site for the database in accordance with the database mapping. User-selected links are also included for executed the dynamic queries. Selection of a link causes a corresponding dynamic query to execute. Relationships between tables in a database can be inferred even when a relationship is not expressly described in schema describing the database. Dynamic queries can be any of sorting, pagination, addition, deletion, and modification queries.

Abstract: A system retrieves a first template associated with data identified in a data request. A second template is generated using the first template and a device description, which is associated with a device generating the data request. The first template is device independent and the second template is associated with the specific device generating the data request as well as the first template. The second template defines a data presentation format for displaying the requested data on the type of device that generated the data request. The second template is stored in a cache, which allows the second template to be used with multiple sets of data without regenerating the template. The requested data is retrieved from a data source and formatted based on the second template. The formatted data is then transmitted to the device generating the data request.

Abstract: A system retrieves a first template associated with data identified in a data request. A second template is generated using the first template and a device description, which is associated with a device generating the data request. The first template is device independent and the second template is associated with the specific device generating the data request as well as the first template. The second template defines a data presentation format for displaying the requested data on the type of device that generated the data request. The second template is stored in a cache, which allows the second template to be used with multiple sets of data without regenerating the template. The requested data is retrieved from a data source and formatted based on the second template. The formatted data is then transmitted to the device generating the data request.