DE10315953A1 - Method and system for generating web pages adapted to client properties - Google Patents

Abstract

The invention relates to a method and a system for automatically generating web pages (5), (6), (7) for client devices (1), (2), (3) of different client types (A), (B), (C) and with different client properties, the client devices (1), (2), (3) with a web server (4) via client requests (14), (16), (18) and server responses (15), (17), (19) communicate and web pages (5), (6), (7) are stored on the web server (4). DOLLAR A On the web server (4) web components (24), (37), (38), (39), (40), (41), (42), (43), (44), (45) and with the client requests (14, (16), (18) sent to the web server (4) the client type (A), (B), (C) and the client properties of the Client devices (1), (2), (3) are identified, from which a profile is read or generated for the respective client devices (1), (2), (3) and the properties of the client Devices (1), (2), (3) are determined DOLLAR A The web components (24), (37), (38), (39), (40), (41), (42), (43 ), (44), (45) are instantiated depending on the properties of the client devices (1), (2), (3) From the instantiated web components (24), (37), (38), (39), (40), (41), (42), (43), (44), (45) representations of the requested web pages (5), (6), (7) are generated and sent to the client Posted.

Description

The The invention relates to a method and a system for generating Web pages for Client devices, whereby the web pages automatically match the type and properties of the client devices be adjusted.

The size Number of currently used different client devices to communicate over the Internet, which includes, for example, PCs, laptops, handheld computers or WAP-enabled mobile phones counting, require for access to the Internet a variety of different web browsers. The different client devices or Device Types have different technical characteristics. For example are their display devices as black and white or color screens from different size and resolution, or their input devices are designed as a keyboard or touchscreen. But also devices with identical properties various web browsers, e.g. Internet Explorer, Netscape or use Opera that supports special functions, which in particular about go beyond the standard language HTML 3.2, sometimes very different.

at The provision of web pages from the Internet is the web server unable to make firm assumptions about the properties of the client device which he transmits the web pages, close. Since different web browsers can be used, it proves it turns out to be difficult, instead of simple HTML pages, mostly uniform for All browsers are created, pages with high ease of use and to offer interactive content, since the use of special complex client-side technologies is necessary, such as Dynamic HTML (Hypertext Mark-up Language), frames, cookies, JavaApplets or ActiveX controls, which are not supported by some browsers, or are supported in different ways in different browsers. This can cause that web pages defective in some browsers or not at all are.

With the future further increasing spread of mobile devices with Internet access, in particular from WAP cell phones, UMTS cell phones, handhelds or PocketPCs, the Web content of the web pages not only for other browsers but for example also for much smaller displays can be processed sensibly.

Presently support the variety of different client devices usually only because of this accomplished that for each client type has its own, sometimes very complex, version of the Web pages is created.

One approach to previous web technologies is to use different web pages or different web programs, such as Active Server Pages, which is described in Williams, A., Barber, K., and P., Newkirk, "Active Server Pages Black Book" , 10 ^th ed., Coriolis Group, 1998, pp. 600, or Java Server Pages, which is described in Hall, M., "Core Servlets and JavaServer Pages", Prentice Hall PTR, 2000, pp. 608 to develop to individually handle the graphical user interface and interaction with each specific client environment.

For this however, the code for each web page in multiple, for the respective client device be created in the corresponding modified form. This inevitably leads to a multiplication of the effort for the creation and maintenance of the Web pages because the web content in all forms of Pages must be created or modified.

On Another disadvantage of previous web technologies for generating web pages, which are adapted to the properties of the different client devices are, it follows that various Internet addresses, so-called URLs (Uniform Resource Locator) for different client types tailored web pages are to be provided.

The The invention is therefore based on the object of a method and a Specify system for creating web pages for client devices whereby the web pages automatically match the type and properties of the client devices can be adjusted to ensure efficient display and minimal maintenance of the web pages too realize.

This Task is accomplished through a process for automatically generating Web pages for client devices of various types Client type and / or with different client properties solved the features specified in claim 1.

advantageous Refinements and a system for generating web pages for client devices of different Client type and with different client properties are specified in further claims.

The basis for the automatic generation of a web page requested by the client devices are the web pages located on a web server, which include one or more registered web components in different variants for the different client devices and browsers and for the respective client device an adapted representation of the requested web page produce.

A The web component is an object in which both the server-side Code and data of the web page are stored and which one provides the web server with a specific set of services, to content for the web pages are suitable prepare.

If the web server made a page request from a client device hereinafter also referred to as a client, it determines the type and the properties of the client, especially the browser, and instantiated for the requested web page the web components which are used for the display of page content for are suitable for this client. Generate the instantiated server-side web components then the page content suitable for the client who requested the page.

alternative there is also the possibility of basically all Instantiate web components of a web page, however even then only for the respective client needed Web components for the generation of the page content can be used.

The Properties of the client include the performance features of the Browsers, such as support for DHTML (Dynamic Hypertext Mark-up Language), cookies or frames, but also the properties of the display, such as PC screens, handhelds or WAP cell phones. The determination of what a client type and browser is preferred based on the information in the corresponding text fields in the http request header (file header a Hyper Text Transfer Protocol request).

After this the instantiated web components the content of the web page for the client generated, transmitted the web server to the client type and to the client properties customized web page to the client.

It is sufficient that the web server for a client who makes a request for a web page only determines once what the client is. A separate session is then generated on the web server for this client (for example, according to the one in Williams, A., Barber, K., and P., Newkirk, “Active Server Pages Black Book”, 10 ^th ed., Coriolis Group, 1998, pp. 600 described procedure), the profile of the client can then be saved in this session.

provides the client now makes further requests to the web server Client profile saved and available on the web server for the Creation of the web page used. If the client for a long time the corresponding session is ended when the web server is no longer accessed.

In an alternative embodiment the client profile on the client, for example in the URL or stored in the form of cookies on the website.

By the invention will support one Variety of different client devices with different ones Browsers efficiently supported in an advantageous manner.

each Web applications that support more than one client device or browser type benefit from the described use of the web components.

The Invention enables it advantageously, the effort for development and maintenance minimize the sides.

Farther Is it possible, the web content of the requested web pages on the different Client devices to optimize optimized, taking the effort for development and maintenance The web content of the pages is different on the different client devices are minimized.

Also for the Variety of increasingly large used mobile devices With internet access, the method according to the invention can be advantageous Be used in such a way that the web content of the web pages also for much smaller displays can be processed sensibly.

Likewise can the web content under only one URL, which is identical for different client devices Tobe offered. It is also not necessary to inquire of the client devices to other, client-dependent Redirect URLs.

Based of embodiments shown in the following drawing figures the invention and advantageous refinements and improvements the invention closer explained and be described.

It demonstrate:

1 Internet access by various Internet-capable clients to a website,

2 a system configuration according to the invention for client-dependent generation, preparation and display of web pages,

3 a procedural sequence of a client request and an automatic construction of a web page,

4 a structure of a web page on a web server, and

5 an embodiment for generating a web page.

1 shows Internet access from various Internet-enabled client devices, such as a PC / workstation 1 , a laptop 2 or a WAP cell phone 3 , on a web server 4 ,

The various client devices are on the Internet or intranet 1 . 2 . 3 used of different types and differ for example in the properties of their screens, their input options or their Internet browser 11 . 12 . 13 ,

The different client devices 1 . 2 . 3 communicate with the web server 4 , on which web pages are stored, in that they request web content from a uniform Internet address (URL) of an Internet service that is identical for all clients, for example http://www.abc.net/index.cgi ,

The web server 4 recognizes the respective type or the properties of the client 1 . 2 . 3 and transmits a suitably generated web page 5 . 6 in possibly different HTML (Hypertext Markup Language) formats to the PC / workstation 1 and the laptop 2 or a page 7 in WML (Wireless Markup Language) format to the WAP-compatible cell phone 3 , This way, all client devices get 1 . 2 . 3 the web content from the same URL, but according to its specific properties.

2 shows a system configuration according to the invention for client-dependent generation, preparation and display of web pages 5 . 6 . 7 using web components.

The different client devices 1 . 2 . 3 communicate with the web server 4 on which the web pages 5 . 6 . 7 are filed via client requests 14 . 16 . 18 and server responses 15 . 17 . 19 ,

Each of the web pages 5 . 6 . 7 contains one or more web components 24 for information processing for the different client types A, B, C of the client devices 1 . 2 . 3 , Depending on the type A, B, C of the respective client 1 . 2 . 3 the properties of the client differ, for example with regard to the screen, the input options such as keyboard and mouse or with regard to the web browser 11 . 12 . 13 , which supports a subset of the existing web technologies with its browser capabilities, for example DHTML, HTML with various document-object models or various data formats such as HTML or WML.

The client devices 1 . 2 . 3 send the client requests 14 . 16 . 18 for a first web page 5 to the web server 4 , The web server 4 evaluates the client requests 14 . 16 . 18 by first typing type A, B, C of the client 1 . 2 . 3 and the browser type 11 . 12 . 13 determined with the associated browser capabilities. The web server then instantiates 4 for the respective client device 1 . 2 . 3 suitable web components 24 in the first page 5 which is the page content for the first page 5 according to the type A, B, C and the properties of the corresponding client 1 . 2 . 3 generated.

The web server then sends 4 that of the selected web components 24 generated first page 5 to the corresponding client 1 . 2 . 3 as a server response 15 . 17 . 19 back. This way every client receives 1 . 2 . 3 an adapted representation of the first page 5 that is optimally read, processed or displayed. Become more web pages 5 . 6 . 7 from the client devices 1 . 2 . 3 requested, the described procedure is run through again.

3 shows a process flow based on process steps 25 - 32 , one from a client 1 . 2 . 3 requested page 5 . 6 . 7 automatically generated and sent to the client 1 . 2 . 3 is sent back.

In a first step 25 becomes a client request 14 . 16 . 18 to the web server 4 transmitted. The request 14 . 16 . 18 contains the URL of the requested page as well as further information about the client in the HTTP request header 1 . 2 . 3 ,

In a second step 26 it checks whether the client 1 . 2 . 3 an inquiry beforehand 14 . 16 . 18 to the web server 4 has put and for the client 1 . 2 . 3 a profile is available. Has already been an inquiry 14 . 17 . 18 a profile with the properties of the client already exists 1 . 2 . 3 which in a third step 27 is only read out.

Is for the client 1 . 2 . 3 however, no profile is available yet, so the web server 4 in a fourth step 28 for the client 1 . 2 . 3 automatically creates a new profile in which the properties of the client are identified in an identification process 1 . 2 . 3 be entered. The information about the client properties, such as browser type and browser capabilities of the client 1 . 2 . 3 , from the HTTP request header used to identify the client type A, B, C.

If it is not possible to create the profile automatically because, for example, a further, very detailed configuration of the client properties is to take place, the identification of the client is carried out in a further embodiment 1 . 2 . 3 realized through a special dialogue. The web server transmits this 4 first an intermediate configuration page to the client 1 . 2 . 3 , On this page the user presents the specific treatment of his client 1 . 2 . 3 for example by selecting from a list of different client types A, B, C.

Now that the client 1 . 2 . 3 was identified, determined in a fifth step 29 the web server 4 for the client devices 1 . 2 . 3 and their browsers 11 . 12 . 13 a profile depending on client properties and skills. The profile is used for later page requests from the client 1 . 2 . 3 stored on the web server.

It is not possible for the client 1 . 2 . 3 or to identify its type A, B, C and its properties is provided in a further embodiment, a corresponding error page to the client 1 . 2 . 3 send back or use a standard profile for the client, for example as a simple HTML client.

In a sixth step 30 instantiates the web server 4 the server-side web components 24 , for the requested web page 5 . 6 . 7 depending on the previously determined client profile.

In a further step 31 is then called by instantiated web components 24 the website 5 . 6 . 7 generated according to the client type A, B, C and the client properties.

In a final step 32 the web server transmits 4 the requested, through the previous steps for the client 1 . 2 . 3 optimally prepared web page 5 . 6 . 7 to the corresponding client device 1 . 2 . 3 ,

In 4 the structure of a web page with its server-side Internet components on a web server is shown.

The website 5 is divided into several function blocks 34 . 35 . 36 , with the function blocks 34 . 35 . 36 for example, menus, static content or form blocks. Each of the function blocks 34 . 35 . 36 assigns one or more web components 37 - 45 on which the content of the corresponding function block in a for the respective client 1 . 2 . 3 appropriate type.

components which belong to the same function block generate web page content which the functions or tasks of the corresponding function block preferably fulfill well, by dividing the part of the page into one for each client type A, B, C represent optimal way.

The first functional block 35 contains, for example, a first web component 37 which is the web content of a first web page 5 generated for type A clients, a second web component 38 , which generates the web content for type B clients and a third web component 39 , which generates the web content for Type C clients.

The second functional block 36 contains, for example, a fourth web component 40 which is the web content of a second web page 6 generated for type A clients, a second web component 41 , which generates the web content for type B clients and a third web component 42 , which generates the web content for Type C clients.

Those responsible for a client type A, B, C, the different function blocks 34 . 35 . 36 associated web components 37 to 45 thus together ensure the construction of the complete web page 5 . 6 . 7 , The resulting, possibly large, number of web components 24 . 37 to 45 can be arranged within a web page according to conventional web page structure models.

5 shows an embodiment for generating a web page 5 and the structure of web page content 46 the web page 5 with the help of the instantiated web components 49 ,

The instantiated web components 49 generate the respective content 47 the web page 5 , The creation of the website content 48 is based on the client properties of the instantiated web components 49 ,

The non-instantiated web components 50 are at the side generation 48 not involved and therefore do not require any resources on the web server at this time.

Claims (15)

Process for the automatic generation of web pages ( 5 ), ( 6 ), ( 7 ) for client devices ( 1 ), ( 2 ), ( 3 ) of different client types (A), (B), (C) and / or with different client properties, the client devices ( 1 ), ( 2 ), ( 3 ) with a web server ( 4 ) about client requests ( 14 ), ( 16 ), ( 18 ) and server responses ( 15 ), ( 17 ), ( 19 ) communicate and on the web server ( 4 ) Web pages ( 5 ), ( 6 ), ( 7 ) are stored, characterized in that - on the web server ( 4 ) Web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) are filed, - with the to the web server ( 4 ) sent client requests ( 14 ), ( 16 ), ( 18 ) the client type (A), (B), (C) and the client properties of the client device ( 1 ), ( 2 ), ( 3 ) are identified - the web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) depending on the properties of the client devices ( 1 ), ( 2 ), ( 3 ) are instantiated, - using the instantiated web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) Representations of the requested web pages ( 5 ), ( 6 ), ( 7 ) generated and transmitted to the client. A method according to claim 1, characterized in that the web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) generated representations of the web pages ( 5 ), ( 6 ), ( 7 ) from the client devices ( 1 ), ( 2 ), ( 3 ) read, processed or displayed. Method according to claim 1 or 2, characterized in that from the identified client properties of the respective client device ( 1 ), ( 2 ), ( 3 ) from the web server ( 4 ) a profile is read in or generated and the properties of the client devices ( 1 ), ( 2 ), ( 3 ) be determined. Method according to one of the preceding claims, characterized in that in the web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) server-side code and data for the web pages ( 5 ), ( 6 ), ( 7 ) get saved. Method according to one of the preceding claims, characterized in that the properties of the client devices ( 1 ), ( 2 ), ( 3 ) Browser type and browser capabilities, properties of the displays and input devices of the client devices ( 1 ), ( 2 ), ( 3 ) include. Method according to one of the preceding claims, characterized in that from the in the web server ( 4 ) determined type (A), (B), (C) and the determined properties of the client devices ( 1 ), ( 2 ), ( 3 ) for the respective client device ( 1 ), ( 2 ), ( 3 ) a separate session is created in which a profile of the respective client device ( 1 ), ( 2 ), ( 3 ) is saved. A method according to claim 6, characterized in that the stored profiles of the client devices ( 1 ), ( 2 ), ( 3 ) for further client requests ( 14 ), ( 16 ), ( 18 ) to the web server ( 4 ) are used until the session on the web server ( 4 ) is ended. Method according to one of claims 1 to 6, characterized in that the profiles of the client devices ( 1 ), ( 2 ), ( 3 ) in the URL or in the form of cookies on the website. Method according to one of the preceding claims, characterized in that in the web server ( 4 ) automatically created profiles for the client devices ( 1 ), ( 2 ), ( 3 ) Information about the properties and type (A), (B), (C) of the respective client device in an identification process ( 1 ), ( 2 ), ( 3 ) from the header of an HTTP request. Method according to one of claims 1 to 8, characterized in that the identification of the client devices ( 1 ), ( 2 ), ( 3 ) is realized via a special dialog, whereby the web server ( 4 } a configuration page to the client device ( 1 ), ( 2 ), ( 3 ) transmitted and by the user of the client device ( 1 ), ( 2 ), ( 3 ) a selection from a list of different client types (A), (B), (C) is carried out. Method according to one of claims 1 to 8, characterized in that the web server ( 4 ) an error page to the client device ( 1 ), ( 2 ), ( 3 ) is sent back or for the client device ( 1 ), ( 2 ), ( 3 ) a standard profile is used if the web server ( 4 ) is unable to connect the client device ( 1 ), ( 2 ), ( 3 ) to identify. System for the automatic generation of web pages ( 5 ), ( 6 ), ( 7 ) for client devices ( 1 ), ( 2 ), ( 3 ) of different client types (A), (B), (C) and / or with different client properties, the client devices ( 1 ), ( 2 ), ( 3 ) with a web server ( 4 ) about client requests ( 14 ), ( 16 ), ( 18 ) and server responses ( 15 ), ( 17 ), ( 19 ) communicate and on the web server ( 4 ) Web pages ( 5 ), ( 6 ), ( 7 ) are stored, characterized in that the web pages ( 1 ), ( 2 ), ( 3 ) Web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) for the automatic generation of representations of the web pages ( 5 ), ( 6 ), ( 7 ) for different client types (A), (B), (C) and different client properties of the client devices ( 1 ), ( 2 ), ( 3 ) include. System according to claim 12, characterized in that the web server ( 4 ) from the client requests ( 14 ), ( 16 ), ( 18 ) the client type (A), (B), (C) and the client properties using the web component ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) that the respective client devices ( 1 ), ( 2 ), ( 3 ) is assigned to the page content of the web pages ( 5 ), ( 6 ), ( 7 ) generated. System according to claim 12 or 13, characterized in that the client properties of the respective client browser type and browser capabilities, properties of the displays and the input devices of the client devices ( 1 ), ( 2 ), ( 3 ) are. System according to one of claims 12 to 14, characterized in that the web server ( 4 ) from the web components ( 24 ), ( 37 ), ( 38 ), ( 39 ), ( 40 ), ( 41 ), ( 42 ), ( 43 ), ( 44 ), ( 45 ) generated representation of the web pages ( 5 ), ( 6 ), ( 7 ) to the respective client device ( 1 ), ( 2 ), ( 3 ) using the server responses ( 15 ), ( 17 ), ( 19 ) returns.