CA2602410A1 - Client-server application development and deployment system and methods - Google Patents

Client-server application development and deployment system and methods Download PDF

Info

Publication number
CA2602410A1
CA2602410A1 CA002602410A CA2602410A CA2602410A1 CA 2602410 A1 CA2602410 A1 CA 2602410A1 CA 002602410 A CA002602410 A CA 002602410A CA 2602410 A CA2602410 A CA 2602410A CA 2602410 A1 CA2602410 A1 CA 2602410A1
Authority
CA
Canada
Prior art keywords
server
recited
tag
client
web
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CA002602410A
Other languages
French (fr)
Other versions
CA2602410C (en
Inventor
Fred B. Dufresne
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Open Invention Network LLC
Original Assignee
Fred B. Dufresne
Cerinet Inc.
Open Invention Network Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US08/642,426 external-priority patent/US5835712A/en
Application filed by Fred B. Dufresne, Cerinet Inc., Open Invention Network Llc filed Critical Fred B. Dufresne
Priority claimed from CA002406547A external-priority patent/CA2406547C/en
Publication of CA2602410A1 publication Critical patent/CA2602410A1/en
Application granted granted Critical
Publication of CA2602410C publication Critical patent/CA2602410C/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Abstract

A system and method for rapid deployment of World Wide Web applications on the Internet. A preferred method provides a template, accessible to both client and server, for constructing Web source text. The source text.includes HTML tag extensions for implementing dynamic Web environment. The tag extensions are nested and grouped to form scripts to perform specific tasks, such as state construction and on-line data arrangement.
Each tag extension or script is expanded and replaced with data value to be embedded within a traditional HTML tag. A processor is employed to process templates and execute tag extensions therein, and produces pages in pure HTML form for displaying by any Web browser.

Claims (361)

1. A system for implementing a state environment within a client-server session using a stateless protocol, comprising a server; and a client;

wherein the server, pursuant to a request for a displayable page from the client, generates a variable for subsequently retrieving state information and causes the variable and the hypertext source to the displayable page to be sent to the client, and, wherein, when the server receives a subsequent request for a subsequent displayable page and the variable from the client, the server retrieves the state information, at the server, to maintain the state environment within the client-server session.
2. The system as recited in Claim 1 wherein the server further updates the state information, stores said updated state information at the server and causes the variable to be sent to the client upon a subsequent request.
3. The system recited in Claim 1 or 2 wherein said application element comprises one or more:
a. ~template(s);
b. ~script(s);
c. ~database record(s);
d. ~global(s); or e. ~any combination of :
i. ~one or more of the template(s);
ii. ~one or more of the script(s);

iii. ~one or more of the database record(s); and/or iv. ~one or more of the global(s).
4. The system recited in Claim 3 wherein the template comprises one or more:
a. ~HTML tag(s);
b. ~tag extension(s); or c. ~any combination of:
i. ~one or more of the HTML tag(s); and ii. ~one or more of the tag extension(s).
5. The system recited in Claim 4 wherein the tag extension comprises a static tag extension or variable tag extension.
6. The system recited in Claim 5 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
7. The system recited in Claim 6 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
8. The system recited in Claim 7 wherein the value identified from the database is static data.
9. The system recited in Claim 8 wherein the displayable pages are Web pages and the client is a Web browser.
10. The system recited in Claim 9 wherein the server is a Web server.
11. The system recited in Claim 10 wherein the Web server comprises an http server and a processor for controlling the http server.
12. The system recited in Claim 7 wherein the corresponding value points to a template.
13. The system recited in Claim 5 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
14. The system recited in Claim 13 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
15. The system recited in Claim 14 wherein the value identified from the database is a variable.
16. The system recited in Claim 15 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
d. one or more of the tag extension(s); and e. one or more of the instruction(s).
17. The system recited in Claim 16 wherein the displayable pages are Web pages and the client is a Web browser.
18. The system recited in Claim 17 wherein the server is a Web server.
19. The system recited in Claim 18 wherein the Web server comprises an http server and a processor for controlling the http server.
20. The system recited in Claim 14 wherein the corresponding value points to a template.
21. The system recited in Claim 4 wherein the tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
22. The system recited in Claim 21 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
23. The system recited in Claim 22 wherein the value identified from the database is static data or a variable.
24. The system recited in Claim 23 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s).
25. The system recited in Claim 24 wherein the displayable pages are Web pages and the client is a Web browser.
26. The system recited in Claim 25 wherein the server is a Web server.
27. The system recited in Claim 26 wherein the Web server comprises an http server and a processor for controlling the http server.
28. The system recited in Claim 22 wherein the corresponding value points to a template.
29. The system recited in Claim 2 wherein the script comprises a collection of one or more:
a. tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s);

executed by the server in sequence to perform a prescribed task.
30. The system recited in Claim 29 wherein the tag extension comprises a static tag extension or variable tag extension.
31. The system recited in Claim 30 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
32. The system recited in Claim 31 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
33. The system recited in Claim 32 wherein the value identified from the database is static data.
34. The system recited in Claim 33 wherein the displayable pages are Web pages and the client is a Web browser.
35. The system recited in Claim 34 wherein the server is a Web server.
36. The system recited in Claim 35, wherein the Web server comprises an http server and a processor for controlling the http server.
37. The system recited in Claim 32 wherein the corresponding value points to a template.
38. The system recited in Claim 30, wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
39. The system recited in Claim 38 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
40. The system recited in Claim 39 wherein the value identified from the database is a variable.
41. The system recited in Claim 40 wherein the displayable pages are Web pages and the client is a Web browser.
42. The system recited in Claim 41 wherein the server is a Web server.
43. The system recited in Claim 42 wherein the Web server comprises an http server and a processor for controlling the http server.
44. The system recited in Claim 39 wherein the corresponding value points to a template.
45. The system recited in Claim 29 wherein the tag extension further comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
46. The system recited in Claim 45 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
47. The system recited in Claim 46 wherein the value identified from the database is static data or a variable.
48. The system recited in Claim 47 wherein the value identified from the database is a variable.
49. The system recited in Claim 48 wherein the displayable pages are Web pages and the client is a Web browser.
50. The system recited in Claim 49 wherein the server is a Web server.
51. The system recited in Claim 50 wherein the Web server comprises an http server and a processor for controlling the http server.
52. The system recited in Claim 46 wherein the corresponding value points to a template.
53. The system recited in Claim 29 wherein the instruction comprises command(s) and/or instruction set(s) created with one or more of the instruction(s) and/or the tag extension(s).
54. The system recited in Claim 53 wherein the displayable pages are Web pages and the client is a Web browser.
55. The system recited in Claim 54 wherein the server is a Web server.
56. The system recited in Claim 55 wherein the Web server comprises an http server and a processor for controlling the http server.
57. The system recited in Claim 3 wherein the global is a package of source code that can exist on a plurality of displayable pages.
58. The system recited in Claim 57 wherein the displayable pages are Web pages and the client is a Web browser.
59. The system recited in Claim 1 or 2 wherein the displayable pages are Web pages and the client is a Web browser.
60. The system recited in Claim 59 wherein the server is a Web server.
61. The system recited in Claim 60 wherein the Web server comprises an http server and a processor for controlling the http server.
62. The system recited in Claim 1 wherein the state information comprises a call to a script that produces new state information, wherein the new state information is retrievable from the variable for subsequently retrieving state information for a hypertext source for a consequent displayable page to be passed to the client.
63. The system recited in Claim 1 or 62 wherein the variable for subsequently retrieving state information is passed to the client through a hidden field.
64. The system recited in Claim 63 wherein the hidden field is an HTML
hidden field.
65. The system recited in Claim 64 wherein the displayable pages are Web pages and the client is a Web browser.
66. The system recited in Claim 65 wherein the server is a Web server.
67. The system recited in Claim 66 wherein the Web server comprises an http server and a processor for controlling the http server.
68. The system recited in Claim 1 or 62 wherein the variable for subsequently retrieving state information is transmitted using a network protocol.
69. The system recited in Claim 1 wherein the state information is passed to the client through a hidden field.
70. The system recited in Claim 69 wherein the hidden field is an HTML
hidden field.
71. The system recited in Claim 70 wherein the displayable pages are Web pages and the client is a Web browser.
72. The system recited in Claim 71 wherein the server is a Web server.
73. The system recited in Claim 72 wherein the Web server comprises an http server and a processor for controlling the http server.
74. A method of implementing a state environment within a client-server session using a stateless protocol, comprising the steps of:

a. pursuant to a request for a displayable page from a client, generating a variable for subsequently retrieving state information;

b. forwarding the variable and the displayable page to the client;

c. when the server receives the variable from the client, retrieving the state information at the server to maintain the state environment within the client-server session.
75. The method recited in Claim 74 wherein said application element comprises one or more:
a. template(s);
b. script(s);
c. database record(s);
d. global(s); or e. any combination of:
i. one or more of the template(s);
ii. one or more of the script(s);
iii. one or more of the database record(s); and/or iv. one or more of the global(s).
76. The method recited in Claim 75 wherein the template comprises one or more:
a. HTML tag(s);
b. tag extension(s); or c. any combination of:
i. one or more of the HTML tag(s); and ii. one or more of the tag extension(s).
77. The method recited in Claim 76 wherein the tag extension comprises a static tag extension or variable tag extension.
78. The method recited in Claim 77 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
79. The method recited in Claim 78 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
80. The method recited in Claim 79 wherein the value identified from the database is static data.
81. The method recited in Claim 80 wherein the displayable pages are Web pages and the client is a Web browser.
82. The method recited in Claim 81 wherein the server is a Web server.
83. The method recited in Claim 82 wherein the Web server comprises an http server and a processor for controlling the http server.
84. The method recited in Claim 79 wherein the corresponding value points to a template.
85. The method recited in Claim 77 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
86. The method recited in Claim 85 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
87. The method recited in Claim 86 wherein the value identified from the database is a variable.
88. The method recited in Claim 87 wherein the variable comprises one or more:
a. ~of the tag extension(s);
b. ~instruction(s); or c. ~any combination of:
i. ~one or more of the tag extension(s); and ii. ~one or more of the instruction(s).
89. The method recited in Claim 88 wherein the displayable pages are Web pages and the client is a Web browser.
90. The method recited in Claim 89 wherein the server is a Web server.
91. The method recited in Claim 90 wherein the Web server comprises an http server and a processor for controlling the http server.
92. The method recited in Claim 86 wherein the corresponding value points to a template.
93. The method recited in Claim 76 wherein the tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
94. The method recited in Claim 93 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
95. The method recited in Claim 94 wherein the value identified from the database is static data or a variable.
96. The method recited in Claim 95 wherein the variable comprises one or more:
a. ~of the tag extension(s);
b. ~instruction(s); or c. ~any combination of:
i. ~one or more of the tag extension(s); and ii. ~one or more of the instruction(s).
97. The method recited in Claim 96 wherein the displayable pages are Web pages and the client is a Web browser.
98. The method recited in Claim 97 wherein the server is a Web server.
99. The method recited in Claim 98 wherein the Web server comprises an http server and a processor for controlling the http server.
100. The method recited in Claim 94 wherein the corresponding value points to a template.
101. The method recited in Claim 75 wherein the script comprises a collection of one or more:
a. ~tag extension(s);
b. ~instruction(s); or c. ~any combination of:
i. ~one or more of the tag extension(s); and ii. ~one or more of the instruction(s);

executed by the server in sequence to perform a prescribed task.
102. The method recited in Claim 101 wherein the tag extension comprises a static tag extension or variable tag extension.
103. The method recited in Claim 102 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
104. The method recited in Claim 103 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
105. The method recited in Claim 104 wherein the value identified from the database is static data.
106. The method recited in Claim 105 wherein the displayable pages are Web pages and the client is a Web browser.
107. The method recited in Claim 106 wherein the server is a Web server.
108. The method recited in Claim 107 wherein the Web server comprises an http server and a processor for controlling the http server.
109. The method recited in Claim 104 wherein the corresponding value points to a template.
110. The method recited in Claim 102 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
111. The method recited in Claim 110 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
112. The method recited in Claim 111 wherein the value identified from the database is a variable.
113. The method recited in Claim 112 wherein the displayable pages are Web pages and the client is a Web browser.
114. The method recited in Claim 113 wherein the server is a Web server.
115. The method recited in Claim 114 wherein the Web server comprises an http server and a processor for controlling the http server.
116. The method recited in Claim 111 wherein the corresponding value points to a template.
117. The method recited in Claim 101 wherein the tag extension further comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
118. The method recited in Claim 117 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
119. The method recited in Claim 118 wherein the value identified from the database is static data or a variable.
120. The method recited in Claim 119 wherein the value identified from the database is a variable.
121. The method recited in Claim 120 wherein the displayable pages are Web pages and the client is a Web browser.
122. The method recited in Claim 121 wherein the server is a Web server.
123. The method recited in Claim 122 wherein the Web server comprises an http server and a processor for controlling the http server.
124. The method recited in Claim 118 wherein the corresponding value points to a template.
125. The method recited in Claim 101 wherein the instruction comprises command(s) and/or instruction set(s) created with one or more of the instruction(s) and/or the tag extension(s).
126. The method recited in Claim 125 wherein the displayable pages are Web pages and the client is a Web browser.
127. The method recited in Claim 126 wherein the server is a Web server.
128. The method recited in Claim 127 wherein the Web server comprises an http server and a processor for controlling the http server.
129. The method recited in Claim 75 wherein the global is a package of source code that can exist on a plurality of displayable pages.
130. The method recited in Claim 129 wherein the displayable pages are Web pages and the client is a Web browser.
131. The method recited in Claim 74 wherein the displayable pages are Web pages and the client is a Web browser.
132. The method recited in Claim 131 wherein the server is a Web server.
133. The method recited in Claim 132 wherein the Web server comprises an http server and a processor for controlling the http server.
134. The method recited in Claim 74 wherein the state information comprises a call to a script that produces new state information, wherein the new state information is retrievable from the variable for subsequently retrieving state information for a hypertext source to a consequent displayable page to be passed to the client.
135. The method recited in Claim 74 or 134 wherein the variable for subsequently retrieving state information is passed to the client through a hidden field.
136. The method recited in Claim 135 wherein the hidden field is an HTML
hidden field.
137. The method recited in Claim 136 wherein the displayable pages are Web pages and the client is a Web browser.
138. The method recited in Claim 137 wherein the server is a Web server.
139. The method recited in Claim 138 wherein the Web server comprises an http server and a processor for controlling the http server.
140. The method recited in Claim 74 or 134 wherein the variable for subsequently retrieving state information is transmitted using a network protocol.
141. The method recited in Claim 74 wherein the state information is passed to the client through a hidden field.
142. The method recited in Claim 141 wherein the hidden field is an HTML
hidden field.
143. The method recited in Claim 142 wherein the displayable pages are Web pages and the client is a Web browser.
144. The method recited in Claim 143 wherein the server is a Web server.
145. The method recited in Claim 144 wherein the Web server comprises an http server and a processor for controlling the http server.
146. A computer readable medium storing executable computer program instructions which, when executed at a server, causes the server to perform a process for implementing a state environment within a client-server session using a stateless protocol, the process comprising the steps of:
a. pursuant to a request for a displayable page from a client, generating a variable for subsequently retrieving state information;
b. forwarding the variable and the displayable page to the client;
c. when the server receives the variable from the client, retrieving the state information at the server to maintain the state environment within the client-server session.
147. The computer readable media recited in Claim 146 wherein said application element comprises one or more:
a. template(s);
b. script(s);
c. database record(s);
d. global(s); or e. any combination of:
i. one or more of the template(s);
ii. one or more of the script(s);
iii. one or more of the database record(s); and/or iv. one or more of the global(s).
148. The computer readable media recited in Claim 147 wherein the template comprises one or more:
a. HTML tag(s);
b. tag extension(s); or c. any combination of:
i. one or more of the HTML tag(s); and ii. one or more of the tag extension(s).
149. The computer readable media recited in Claim 148 wherein the tag extension comprises a static tag extension or variable tag extension.
150. The computer readable media recited in Claim 149 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
151. The computer readable media recited in Claim 150 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
152. The computer readable media recited in Claim 151 wherein the value identified from the database is static data.
153. The computer readable media recited in Claim 152 wherein the displayable pages are Web pages and the client is a Web browser.
154. The computer readable media recited in Claim 153 wherein the server is a Web server.
155. The computer readable media recited in Claim 154 wherein the Web server comprises an http server and a processor for controlling the http server.
156. The computer readable media recited in Claim 151 wherein the corresponding value points to a template.
157. The computer readable media recited in Claim 149 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
158. The computer readable media recited in Claim 157 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
159. The computer readable media recited in Claim 158 wherein the value identified from the database is a variable.
160. The computer readable media recited in Claim 159 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
d. one or more of the tag extension(s); and e. one or more of the instruction(s).
161. The computer readable media recited in Claim 160 wherein the displayable pages are Web pages and the client is a Web browser.
162. The computer readable media recited in Claim 161 wherein the server is a Web server.
163. The computer readable media recited in Claim 162 wherein the Web server comprises an http server and a processor for controlling the http server.
164. The computer readable media recited in Claim 158 wherein the corresponding value points to a template.
165. The computer readable media recited in Claim 148 wherein the tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
166. The computer readable media recited in Claim 165 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
167. The computer readable media recited in Claim 166 wherein the value identified from the database is static data or a variable.
168. The computer readable media recited in Claim 167 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s).
169. The computer readable media recited in Claim 168 wherein the displayable pages are Web pages and the client is a Web browser.
170. The computer readable media recited in Claim 169 wherein the server is a Web server.
171. The computer readable media recited in Claim 170 wherein the Web server comprises an http server and a processor for controlling the http server.
172. The computer readable media recited in Claim 166 wherein the corresponding value points to a template.
173. The computer readable media recited in Claim 147 wherein the script comprises a collection of one or more:
a. tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s);

executed by the server in sequence to perform a prescribed task.
174. The computer readable media recited in Claim 173 wherein the tag extension comprises a static tag extension or variable tag extension.
175. The computer readable media recited in Claim 174 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
176. The computer readable media recited in Claim 175 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
177. The computer readable media recited in Claim 176 wherein the value identified from the database is static data.
178. The computer readable media recited in Claim 177 wherein the displayable pages are Web pages and the client is a Web browser.
179. The computer readable media recited in Claim 178 wherein the server is a Web server.
180. The computer readable media recited in Claim 179 wherein the Web server comprises an http server and a processor for controlling the http server.
181. The computer readable media recited in Claim 176 wherein the corresponding value points to a template.
182. The computer readable media recited in Claim 174 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
183. The computer readable media recited in Claim 182 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
184. The computer readable media recited in Claim 183 wherein the value identified from the database is a variable.
185. The computer readable media recited in Claim 184 wherein the displayable pages are Web pages and the client is a Web browser.
186. The computer readable media recited in Claim 185 wherein the server is a Web server.
187. The computer readable media recited in Claim 186 wherein the Web server comprises an http server and a processor for controlling the http server.
188. The computer readable media recited in Claim 183 wherein the corresponding value points to a template.
189. The computer readable media recited in Claim 173 wherein the tag extension further comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
190. The computer readable media recited in Claim 189 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
191. The computer readable media recited in Claim 190 wherein the value identified from the database is static data or a variable.
192. The computer readable media recited in Claim 191 wherein the value identified from the database is a variable.
193. The computer readable media recited in Claim 192 wherein the displayable pages are Web pages and the client is a Web browser.
194. The computer readable media recited in Claim 193 wherein the server is a Web server.
195. The computer readable media recited in Claim 194 wherein the Web server comprises an http server and a processor for controlling the http server.
196. The computer readable media recited in Claim 190 wherein the corresponding value points to a template.
197. The computer readable media recited in Claim 173 wherein the instruction comprises command(s) and/or instruction set(s) created with one or more of the instruction(s) and/or the tag extension(s).
198. The computer readable media recited in Claim 197 wherein the displayable pages are Web pages and the client is a Web browser.
199. The computer readable media recited in Claim 198 wherein the server is a Web server.
200. The computer readable media recited in Claim 199 wherein the Web server comprises an http server and a processor for controlling the http server.
201. The computer readable media recited in Claim 147 wherein the global is a package of source code that can exist on a plurality of displayable pages.
202. The computer readable media recited in Claim 201 wherein the displayable pages are Web pages and the client is a Web browser.
203. The computer readable media recited in Claim 146 wherein the displayable pages are Web pages and the client is a Web browser.
204. The computer readable media recited in Claim 203 wherein the server is a Web server.
205. The computer readable media recited in Claim 204 wherein the Web server comprises an http server and a processor for controlling the http server.
206. The computer readable media recited in Claim 146 wherein the state information comprises a call to a script that produces new state information, wherein the new state information is retrievable from the variable for subsequently retrieving state information for a hypertext source to a consequent displayable page to be passed to the client.
207. The computer readable media recited in Claim 146 or 206 wherein the variable for subsequently retrieving state information is passed to the client through a hidden field.
208. The computer readable media recited in Claim 207 wherein the hidden field is an HTML hidden field.
209. The computer readable media recited in Claim 208 wherein the displayable pages are Web pages and the client is a Web browser.
210. The computer readable media recited in Claim 209 wherein the server is a Web server.
211. The computer readable media recited in Claim 210 wherein the Web server comprises an http server and a processor for controlling the http server.
212. The computer readable media recited in Claim 146 or 206 wherein the variable for subsequently retrieving state information is transmitted using a network protocol.
213. The computer readable media recited in Claim 146 wherein the state information is passed to the client through a hidden field.
214. The computer readable media recited in Claim 213 wherein the hidden field is an HTML hidden field.
215. The computer readable media recited in Claim 214 wherein the displayable pages are Web pages and the client is a Web browser.
216. The computer readable media recited in Claim 215 wherein the server is a Web server.
217. The computer readable media recited in Claim 216 wherein the Web server comprises an http server and a processor for controlling the http server.
218. A method of implementing a state environment within a client-server session comprising:

receiving at a server a request from a client for a displayable page;
generating a variable for subsequently retrieving state information;
sending the variable and the displayable page to the client;

when the server receives a subsequent request for a subsequent displayable page from the client, wherein the subsequent request comprises said variable, and a call to the server, causing the server to retrieve said state information and to generate new state information; and sending the variable for the new state information and the source to the subsequent displayable page to the client.
219. The method recited in Claim 218 wherein said application element comprises one or more:
a. template(s);
b. script(s);
c. database record(s);
d. global(s); or e. any combination of :
i. one or more of the template(s);
ii. one or more of the script(s);
iii. one or more of the database record(s); and/or iv. one or more of the global(s).
220. The method recited in Claim 219 wherein the template comprises one or more:
a. HTML tag(s);
b. tag extension(s); or c. any combination of:

i. one or more of the HTML tag(s); and ii. one or more of the tag extension(s).
221. The method recited in Claim 220 wherein the tag extension comprises a static tag extension or variable tag extension.
222. The method recited in Claim 221 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
223. The method recited in Claim 222 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
224. The method recited in Claim 223 wherein the value identified from the database is static data.
225. The method recited in Claim 224 wherein the displayable pages are Web pages and the client is a Web browser.
226. The method recited in Claim 225 wherein the server is a Web server.
227. The method recited in Claim 226 wherein the Web server comprises an http server and a processor for controlling the http server.
228. The method recited in Claim 223 wherein the corresponding value points to a template.
229. The method recited in Claim 221 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
230. The method recited in Claim 229 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
231. The method recited in Claim 230 wherein the value identified from the database is a variable.
232. The method recited in Claim 231 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
d. one or more of the tag extension(s); and e. one or more of the instruction(s).
233. The method recited in Claim 232 wherein the displayable pages are Web pages and the client is a Web browser.
234. The method recited in Claim 233 wherein the server is a Web server.
235. The method recited in Claim 234 wherein the Web server comprises an http server and a processor for controlling the http server.
236. The method recited in Claim 230 wherein the corresponding value points to a template.
237. The method recited in Claim 220 wherein the tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
238. The method recited in Claim 237 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
239. The method recited in Claim 238 wherein the value identified from the database is static data or a variable.
240. The method recited in Claim 239 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s).
241. The method recited in Claim 240 wherein the displayable pages are Web pages and the client is a Web browser.
242. The method recited in Claim 241 wherein the server is a Web server.
243. The method recited in Claim 242 wherein the Web server comprises an http server and a processor for controlling the http server.
244. The method recited in Claim 238 wherein the corresponding value points to a template.
245. The method recited in Claim 219 wherein the script comprises a collection of one or more:
a. tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s);

executed by the server in sequence to perform a prescribed task.
246. The method recited in Claim 245 wherein the tag extension comprises a static tag extension or variable tag extension.
247. The method recited in Claim 246 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
248. The method recited in Claim 247 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
249. The method recited in Claim 248 wherein the value identified from the database is static data.
250. The method recited in Claim 249 wherein the displayable pages are Web pages and the client is a Web browser.
251. The method recited in Claim 250 wherein the server is a Web server.
252. The method recited in Claim 251 wherein the Web server comprises an http server and a processor for controlling the http server.
253. The method recited in Claim 248 wherein the corresponding value points to a template.
254. The method recited in Claim 246 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
255. The method recited in Claim 254 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
256. The method recited in Claim 255 wherein the value identified from the database is a variable.
257. The method recited in Claim 256 wherein the displayable pages are Web pages and the client is a Web browser.
258. The method recited in Claim 257 wherein the server is a Web server.
259. The method recited in Claim 258 wherein the Web server comprises an http server and a processor for controlling the http server.
260. The method recited in Claim 255 wherein the corresponding value points to a template.
261. The method recited in Claim 245 wherein the tag extension further comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
262. The method recited in Claim 261 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
263. The method recited in Claim 262 wherein the value identified from the database is static data or a variable.
264. The method recited in Claim 263 wherein the value identified from the database is a variable.
265. The method recited in Claim 264 wherein the displayable pages are Web pages and the client is a Web browser.
266. The method recited in Claim 265 wherein the server is a Web server.
267. The method recited in Claim 266 wherein the Web server comprises an http server and a processor for controlling the http server.
268. The method recited in Claim 262 wherein the corresponding value points to a template.
269. The method recited in Claim 245 wherein the instruction comprises command(s) and/or instruction set(s) created with one or more of the instruction(s) and/or the tag extension(s).
270. The method recited in Claim 269 wherein the displayable pages are Web pages and the client is a Web browser.
271. The method recited in Claim 270 wherein the server is a Web server.
272. The method recited in Claim 271 wherein the Web server comprises an http server and a processor for controlling the http server.
273. The method recited in Claim 219 wherein the global is a package of source code that can exist on a plurality of displayable pages.
274. The method recited in Claim 273 wherein the displayable pages are Web pages and the client is a Web browser.
275. The method recited in Claim 218 wherein the displayable pages are Web pages and the client is a Web browser.
276. The method recited in Claim 275 wherein the server is a Web server.
277. The method recited in Claim 276 wherein the Web server comprises an http server and a processor for controlling the http server.
278. The method recited in Claim 218 wherein the state information comprises a call to a script that produces new state information, wherein the new state information is retrievable from the variable for subsequently retrieving state information for a hypertext source to a consequent displayable page to be passed to the client.
279. The method recited in Claim 218 or 278 wherein the variable for subsequently retrieving state information is passed to the client through a hidden field.
280. The method recited in Claim 279 wherein the hidden field is an HTML
hidden field.
281. The method recited in Claim 280 wherein the displayable pages are Web pages and the client is a Web browser.
282. The method recited in Claim 281 wherein the server is a Web server.
283. The method recited in Claim 282 wherein the Web server comprises an http server and a processor for controlling the http server.
284. The method recited in Claim 218 or 278 wherein the variable for subsequently retrieving state information is transmitted using a network protocol.
285. The method recited in Claim 218 wherein the state information is passed to the client through a hidden field.
286. The method recited in Claim 285 wherein the hidden field is an HTML
hidden field.
287. The method recited in Claim 286 wherein the displayable pages are Web pages and the client is a Web browser.
288. The method recited in Claim 287 wherein the server is a Web server.
289. The method recited in Claim 288 wherein the Web server comprises an http server and a processor for controlling the http server.
290. A system for implementing a state environment within a client-server session via a stateless protocol, comprising:

a server for receiving a request from a client for a displayable page, for generating a variable for subsequently retrieving state information, for sending the variable and the source to the displayable page to the client, and for, when the server receives a subsequent request for a subsequent displayable page from the client, wherein the subsequent request comprising any input, the variable and a call to the server, causing to generate a new sate information and sending the variable for the new state information and the source to the subsequent displayable page to the client; and the client.
291. The system recited in Claim 290 wherein said application element comprises one or more:
a. template(s);
b. script(s);
c. database record(s);
d. global(s); or e. any combination of:
i. one or more of the template(s);
ii. one or more of the script(s);
iii. one or more of the database record(s); and/or iv. one or more of the global(s).
292. The system recited in Claim 291 wherein the template comprises one or more:
a. HTML tag(s);
b. tag extension(s); or c. any combination of:
i. one or more of the HTML tag(s); and
293. The system recited in Claim 292wherein the tag extension comprises a static tag extension or variable tag extension.
294. The system recited in Claim 293 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
295. The system recited in Claim 294 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
296. The system recited in Claim 295 wherein the value identified from the database is static data.
297. The system recited in Claim 296 wherein the displayable pages are Web pages and the client is a Web browser.
298. The system recited in Claim 297 wherein the server is a Web server.
299. The system recited in Claim 298 wherein the Web server comprises an http server and a processor for controlling the http server.
300. The system recited in Claim 295 wherein the corresponding value points to a template.
301. The system recited in Claim 293 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
302. The system recited in Claim 301 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
303. The system recited in Claim 302 wherein the value identified from the database is a variable.
304. The system recited in Claim 303 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
d. one or more of the tag extension(s); and e. one or more of the instruction(s).
305. The system recited in Claim 304 wherein the displayable pages are Web pages and the client is a Web browser.
306. The system recited in Claim 305 wherein the server is a Web server.
307. The system recited in Claim 306 wherein the Web server comprises an http server and a processor for controlling the http server.
308. The system recited in Claim 302 wherein the corresponding value points to a template.
309. The system recited in Claim 292 wherein the tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, the hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
310. The system recited in Claim 309 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
311. The system recited in Claim 310 wherein the value identified from the database is static data or a variable.
312. The system recited in Claim 311 wherein the variable comprises one or more:
a. of the tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s).
313. The system recited in Claim 312 wherein the displayable pages are Web pages and the client is a Web browser.
314. The system recited in Claim 313 wherein the server is a Web server.
315. The system recited in Claim 314 wherein the Web server comprises an http server and a processor for controlling the http server.
316. The system recited in Claim 310 wherein the corresponding value points to a template.
317. The system recited in Claim 291 wherein the script comprises a collection of one or more:
a. tag extension(s);
b. instruction(s); or c. any combination of:
i. one or more of the tag extension(s); and ii. one or more of the instruction(s);

executed by the server in sequence to perform a prescribed task.
318. The system recited in Claim 317 wherein the tag extension comprises a static tag extension or variable tag extension.
319. The system recited in Claim 318 wherein the static tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
320. The system recited in Claim 319 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
321. The system recited in Claim 320 wherein the value identified from the database is static data.
322. The system recited in Claim 321 wherein the displayable pages are Web pages and the client is a Web browser.
323. The system recited in Claim 322 wherein the server is a Web server.
324. The system recited in Claim 323 wherein the Web server comprises an http server and a processor for controlling the http server.
325. The system recited in Claim 320 wherein the corresponding value points to a template.
326. The system recited in Claim 318 wherein the variable tag extension comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
327. The system recited in Claim 326 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
328. The system recited in Claim 327 wherein the value identified from the database is a variable.
329. The system recited in Claim 328 wherein the displayable pages are Web pages and the client is a Web browser.
330. The system recited in Claim 329 wherein the server is a Web server.
331. The system recited in Claim 330 wherein the Web server comprises an http server and a processor for controlling the http server.
332. The system recited in Claim 327 wherein the corresponding value points to a template.
333. The system recited in Claim 317 wherein the tag extension further comprises an executable tag, wherein, in response to a request for the displayable page from any client to the server, a hypertext source to the displayable page is processed at the server, by executing the executable tag in the hypertext source, prior to forwarding the hypertext source to said any client.
334. The system recited in Claim 333 wherein the executable tag identifies from a database a value such that executing the executable tag replaces the executable tag with the corresponding value.
335. The system recited in Claim 334 wherein the value identified from the database is static data or a variable.
336. The system recited in Claim 335 wherein the value identified from the database is a variable.
337. The system recited in Claim 336 wherein the displayable pages are Web pages and the client is a Web browser.
338. The system recited in Claim 337 wherein the server is a Web server.
339. The system recited in Claim 338 wherein the Web server comprises an http server and a processor for controlling the http server.
340. The system recited in Claim 334 wherein the corresponding value points to a template.
341. The system recited in Claim 317 wherein the instruction comprises command(s) and/or instruction set(s) created with one or more of the instruction(s) and/or the tag extension(s).
342. The system recited in Claim 341 wherein the displayable pages are Web pages and the client is a Web browser.
343. The system recited in Claim 342 wherein the server is a Web server.
344. The system recited in Claim 343 wherein the Web server comprises an http server and a processor for controlling the http server.
345. The system recited in Claim 291 wherein the global is a package of source code that can exist on a plurality of displayable pages.
346. The system recited in Claim 345 wherein the displayable pages are Web pages and the client is a Web browser.
347. The system recited in Claim 290 wherein the displayable pages are Web pages and the client is a Web browser.
348. The system recited in Claim 347 wherein the server is a Web server.
349. The system recited in Claim 348 wherein the Web server comprises an http server and a processor for controlling the http server.
350. The system recited in Claim 290 wherein the state information comprises a call to a script that produces new state information wherein the new state information is retrievable from the variable for subsequently retrieving state information for a hypertext source to a consequent displayable page to be passed to the client.
351. The system recited in Claim 290 or 350 wherein the variable for subsequently retrieving state information is passed to the client through a hidden field.
352. The system recited in Claim 351 wherein the hidden field is an HTML
hidden field.
353. The system recited in Claim 352 wherein the displayable pages are Web pages and the client is a Web browser.
354. The system recited in Claim 353 wherein the server is a Web server.
355. The system recited in Claim 354 wherein the Web server comprises an http server and a processor for controlling the http server.
356. The system recited in Claim 290 or 350 wherein the variable for subsequently retrieving state information is transmitted using a network protocol.
357. The system recited in Claim 290 wherein the state information is passed to the client through a hidden field.
358. The system recited in Claim 357 wherein the hidden field is an HTML
hidden field.
359. The system recited in Claim 358 wherein the displayable pages are Web pages and the client is a Web browser.
360. The system recited in Claim 359 wherein the server is a Web server.
361. The system recited in Claim 360 wherein the Web server comprises an http server and a processor for controlling the http server.
CA2602410A 1996-05-03 1997-05-02 Client-server application development and deployment system and methods Expired - Lifetime CA2602410C (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US08/642,426 US5835712A (en) 1996-05-03 1996-05-03 Client-server system using embedded hypertext tags for application and database development
US08/642,426 1996-05-03
CA002406547A CA2406547C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CA002406547A Division CA2406547C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods

Publications (2)

Publication Number Publication Date
CA2602410A1 true CA2602410A1 (en) 1997-11-13
CA2602410C CA2602410C (en) 2012-10-09

Family

ID=38686973

Family Applications (5)

Application Number Title Priority Date Filing Date
CA2602403A Expired - Lifetime CA2602403C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods
CA2602410A Expired - Lifetime CA2602410C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods
CA002602943A Expired - Lifetime CA2602943C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods
CA2602949A Expired - Lifetime CA2602949C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods
CA2602407A Expired - Lifetime CA2602407C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CA2602403A Expired - Lifetime CA2602403C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods

Family Applications After (3)

Application Number Title Priority Date Filing Date
CA002602943A Expired - Lifetime CA2602943C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods
CA2602949A Expired - Lifetime CA2602949C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods
CA2602407A Expired - Lifetime CA2602407C (en) 1996-05-03 1997-05-02 Client-server application development and deployment system and methods

Country Status (1)

Country Link
CA (5) CA2602403C (en)

Also Published As

Publication number Publication date
CA2602407A1 (en) 1997-11-13
CA2602949A1 (en) 1997-11-13
CA2602403A1 (en) 1997-11-13
CA2602410C (en) 2012-10-09
CA2602943C (en) 2009-07-14
CA2602403C (en) 2013-03-12
CA2602949C (en) 2013-03-12
CA2602943A1 (en) 1997-11-13
CA2602407C (en) 2014-10-07

Similar Documents

Publication Publication Date Title
US5805442A (en) Distributed interface architecture for programmable industrial control systems
US7376653B2 (en) Creating dynamic web pages at a client browser
US7464381B1 (en) Content update proxy method
US8826144B2 (en) Content recovery mode for portlets
US6178433B1 (en) Method and system for generating materials for presentation on a non-frame capable web browser
US8539330B2 (en) Method and system for dynamic web page breadcrumbing using javascript
US7490138B2 (en) System for distributed programmable control
US6819343B1 (en) Dynamic controls for use in computing applications
CA2799486C (en) Client-server application development and deployment system and methods
US6175864B1 (en) Method and apparatus for storyboard scripting of application programs running on a computer system
US6209029B1 (en) Method and apparatus for accessing data sources in a three tier environment
US20060123356A1 (en) Dynamic and updateable computing application panes
US20070061700A1 (en) Initial server-side content rendering for client-script web pages
JPH1124980A (en) Device and method for managing medium accessing plural medium types
EP1275047A1 (en) Dynamic integration of web sites
KR20030064828A (en) Method and system for fulfilling requests for information from a network client
EP1952274A1 (en) A method and system for developing interactive web applications in a unified framework
US7124399B2 (en) Document/view application development architecture applied to ActiveX technology for web based application delivery
US20040205488A1 (en) Active web page for editing with any browser
US20040158617A1 (en) Methods and systems for processing a link
JPH10187512A (en) Method for generating program for database structuring and database operation
US20030079039A1 (en) Web server utilizing a state machine and user token
CA2602410A1 (en) Client-server application development and deployment system and methods
KR100452470B1 (en) Control Method of Gauce system in internet environment
Li HTML5 Based Ajax and SSE Technology with Server Intelligent Instant Messaging to Meet the Needs of Transactional Websites

Legal Events

Date Code Title Description
EEER Examination request
MKEX Expiry

Effective date: 20170502