Serving signals

• US 20060168516A1
• Filed: 03/23/2006
• Published: 07/27/2006
• Est. Priority Date: 05/15/1995
• Status: Abandoned Application

• Current Assignee: Ablaise Limited
• Original Assignee: Ablaise Limited
• Inventors: Bradshaw, Jonathan Marsden, Ritchie, Andrew MacGregor
• Application Number:
  US11/386,697
• Publication Number:
  US 20060168516A1
• Time in Patent Office: Days
• US Class Current: 715/255
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 40/186 Templates
• CPC Class Codes: G06Q 20/1085 involving automatic teller machines [ATMs]
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

Output signals are served from a serving device to a plurality of browsing devices connected to a network. The output signals represent commands executable by each browsable device so as to display viewable data in accordance with specified page formatting. Requests from browsing clients are identified which contain information relating to the data itself and the display format for the data. The data is read and processed so as to combine a representation of the viewable data with executable instructions. The signals are then supplied to requesting browsing devices, after effectively being assembled as a real time o-line process.

Claims

1. A method of responding to an HTTP request, comprising the steps of:

processing said request so as to determine whether the request satisfies an acceptable structure; and

processing data elements contained within said request if it is determined that said structure is acceptable.

2. A method according to claim 1, wherein said request is in the form of a URL.

3. A method according to claim 1, wherein said request satisfies an acceptable structure if each of said data elements satisfies an established format.

4. A method according to claim 1, wherein at least one of said data elements identifies data that is required in response to said request.

5. A method according to claim 1, wherein at least one of said data elements identifies the type of formatting required to data supplied in response to said request.

6. A method according to claim 1, wherein at least one of said data elements comprises information relating to a user.

7. A method according to claim 1, wherein at least one of said data elements is a check sum.

8. A method according to claim 7, wherein said request does not satisfy an acceptable structure if the check sum is invalid.

9. A method of responding to a request, wherein said request is in the form of a URL and includes at least one data element, comprising the steps of:

processing said request so as to determine whether the data element is placed within an established format; and

processing said data element if it is determined that said data element is placed within an established format.

10. Apparatus for responding to an HTTP request, comprising a processor configured to:

process said request so as to determine whether the request satisfies an acceptable structure; and

process data elements contained within said request if it is determined that said structure is acceptable.

11. Apparatus according to claim 10, wherein said request is in the form of a URL.

12. Apparatus according to claim 10, wherein said request satisfies an acceptable structure if each of said data elements is placed within an established format.

13. Apparatus according to claim 10, wherein at least one of said data elements identifies data that is required in response to said request.

14. Apparatus according to claim 10, wherein at least one of said data elements identifies the type of formatting required to data supplied in response to said request.

15. Apparatus according to claim 10, wherein at least one of said data elements comprises information relating to a user.

16. Apparatus according to claim 10, wherein at least one of said data elements is a check sum.

17. Apparatus according to claim 15, wherein said request does not satisfy an acceptable structure if the check sum is invalid.