US20140244735A1 - Streaming server administration protocol - Google Patents
Streaming server administration protocol Download PDFInfo
- Publication number
- US20140244735A1 US20140244735A1 US14/275,313 US201414275313A US2014244735A1 US 20140244735 A1 US20140244735 A1 US 20140244735A1 US 201414275313 A US201414275313 A US 201414275313A US 2014244735 A1 US2014244735 A1 US 2014244735A1
- Authority
- US
- United States
- Prior art keywords
- path name
- container
- server
- snapshot
- data
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H04L67/42—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
Definitions
- the present invention relates generally to protocols and more particularly to a network based administration protocol.
- Server administrators have traditionally used operating system commands, calls and functions to obtain internal server data. With these commands, the server administrator can typically display the server status, display the number of current connections and the detailed information for each connection, display the configuration options for the server, display the configuration options for each server module extension, modify the configuration options for server and module extension, display all server module extensions, display real-time statistics for the server, for example, average number of connections, what streaming applications are being selected and their frequency of selection, the current number of connections and bandwidth used, and display the entire server state for debugging and servicing of problems.
- Examples of such configuration options referred to above include, the maximum number of connections allowed, the default server directory or list of directories, the maximum or minimum buffer size, the time interval for a process or function, the time duration for a process or function, error messages, enable or disable features, a file or list of files for a feature, or a user or list of users for a feature.
- a web server can dynamically create URL's to different streaming servers to load balance across multiple servers or networks.
- a web server providing an access page to the streaming servers can dynamically create browser URL's to allow, deny, or redirect access to different streaming files to load balance or control access to users.
- a network software application like a streaming server which would allow server administrators to access server data from any user device in a network. It would be further desirous to provide a streaming server which would allow server administrators to access such data remotely in real time. It would be advantageous to software creators to provide a server data administration feature requiring a minimum of software changes to existing HTTP based software tools in order to gather information, change information or work with new information stored in a network software application
- a novel protocol is implemented in a streaming server module for real time access to network software data from any location within a computer network in which the server resides.
- the novel protocol supports the use of standard network software programs like web server CGIs and HTTP client software like web browsers for accessing the data from any user device connected to the network or local to the server.
- the internal network software data structures are modified using the invention's protocol syntax to support a connected network client software program.
- the protocol relies on upon the URI mechanism for specifying a container entity using a path, and HTTP 1.0 for specifying request and response mechanisms.
- the goal of the protocol is to remove the usual administration protocol mapping between a command and the data it references, and replace this function with a simple HTTP based command with a URI formatted data specifier
- a feature of the present invention is that the server data is obtainable remotely through the network or locally at the server.
- a further feature of the present invention is that the administration protocol does not require network transport support.
- Still further features of the present invention are the ability to provide within the protocol password protected access to the server data whether accessed locally or remotely and multiple simultaneous administrator requests. Another feature is that the protocol allows data discovery and retrieval with various data types, for example, character, integer and floating point.
- protocol of the present invention is the ability to provide read and write permissions to the information provided by the access to the server data, and the ability to modify the server state such as session, server and preferences.
- the request and response for server data is formatted as an HTTP GET request and response.
- the response data from the server may also be HTML or XML formatted.
- protocol allows for specific data requests of server data, server side data filtering, setting of server attributes, adding, removing and setting server data elements and values, and multiple filters per request for data coherency and performance.
- FIG. 1 is a schematic block diagram of a network constructed according to the principals of the present invention.
- FIG. 2 is a flow chart of an exemplary process of the present invention.
- Network 10 constructed according to the principles of the present invention.
- Network 10 includes a server 12 and a client 14 , the communication between the server 12 and the client 14 may be either directly connected or through another medium 16 , which may be any of a local area network, wide area network, the Internet, or any other proprietary or public network.
- Each of the server 12 and client 14 respectively have associated therewith a computer readable medium 18 , 20 , for storing of programs which implement the processes, procedures and methods of the herein below described inventive protocol.
- the server 12 receives an HTTP path name, as indicated at 30 .
- a decision is made whether an administrative module is identified in the path name. If not and the path name identifies, for example, a typical HTML page, the server would send the HTML page, as indicated at 34 . If yes, as indicated at 36 , the server 12 process the novel protocol of the present invention, as described in detail herein below.
- the administrative data is sent to the client 14 , as indicated at 38 .
- the novel protocol of the present invention support use of CGI's or HTTP client software to develop monitoring and administration software to obtain server data of the type particularly useful to server administrators.
- CGI's or HTTP client software to develop monitoring and administration software to obtain server data of the type particularly useful to server administrators.
- abstraction from the internal server data structure of the server on which the protocol resides is required as well as changes to such internal data structure, to support the requests described in greater detail herein below.
- the novel protocol of the present invention also allows for network or local access by server administrators to internal server data.
- the protocol does not require network transport support.
- the protocol of the present invention relies upon the URI mechanism as defined by RFC2396 for specifying a container entity using a path and HTTP 1.0 RFC 1945 for specifying request and response mechanisms.
- access to internal server data may be obtained through client software by using the familiar path name of a URL in conventional client software, wherein the path name specifies a container from which such data may be obtained.
- a path name may be written as URL/module/admin/, wherein module/admin/ is the container. It will become readily apparent from the description herein below that the use of the URL can retrieve data from various levels of container data.
- the protocol of the present invention in addition to supporting the URL path name, also supports CGI scripting at the server so that commands may be added to the path name.
- HTTP GET is the primary request method. HTTP POST can be used to perform multiple data requests.
- the session is closed at the end of each HTTP request response.
- Body URL filters are not required.
- Administration URL references directed to the server must specify the “/qtss” base segment and the admin module “/admin”.
- the path names are significant for routing the request to the appropriate request handler.
- path/ /is defined as any container in the “path” reference
- path/* is defined as all elements contained in the “path” reference
- a path represents a virtual hierarchical data structure of containers and is expressed as a URL.
- the path terminates with an element.
- the terminating element may be a container.
- Elements are arrays. If there is a single element in the array, then the following URL queries are equivalent: “path/element”, “path/element/”, “path/element/*”, and “path/element/1” are all evaluated as the same query.
- a URI without a ‘?’ defaults to a GET request
- Query options are not case sensitive. Query option values are case sensitive. Unknown query options are ignored. Query options not required by a command are ignored.
- the GET does not require other query options
- command SET ⁇ set data identified by URI
- the command sets the element value referenced by the URL.
- type ⁇ if defined then type checking of the server element type and the set type is performed. If a match of the stored type and the request type fails, an error is returned an the command fails.
- command DEL ⁇ delete data identified by the URI.
- the command deletes the element referenced by the URL.
- command ADD ⁇ add data identified by the URI. If the element at the end of the URL is an element the ADD performs an add to the array of elements referenced by the element name.
- Data types can be any server allowed text value. New data types can be defined and returned by the server.
- the data types are: Uint8, Sint8, Uint16, Sint16, Uint32, Sint32, Uint64, Sint64, Float32, Float64, Boo18, Bool16, CharArray, QTSS_Object, and void pointer.
- QTSS_Objects, pointers and unknown data types always convert to a host ordered hex value. The values converted are returned in hex. AN example is when adding a new attribute to the server. If the type is not known by the server, then the value returned will be a string of hex values.
- a snapshot is the container of values from which an admin response is generated (the measured values at a particular point in time, as compared to the constantly changing values). There is one active snapshot per admin connection. Each request without a snapshot in the URI generates a new snapshot. There is only one current snapshot per request. Each new snapshot invalidates the previous per admin connection snapshot.
- a snapshot is a hierarchy of containers specifying the type, name, value and read/write attribute of values copied from the server's internal structures using the module API (Application Program Interface)
- Snapshots are always complete copies of the referenced resources, however, the returned data can be filtered by specifying the desired fields in the body of a request.
- a GET without a snapshot query value is a request which automatically makes a new snapshot. If the snapshot is not returned by the server, then snapshots are not supported.
- a POST contains the default set of objects in the URL.
- the POST body can contain multiple sub URL's performing multiple SET, GET or DEL command operations on the set of data represented by the default URL.
- Filters specify a subset of data to be returned on each request. Multiple filters are evaluated in order with each result placed in the response.
- Filter defined attributes replace any previous attributes settings for each filter response.
- the request URI is the default filter. New filters override the parameters defined by the request URI.
- the error state for the request is always reported with each response at the end of the data.
- the entities' name and their values are located in the request body. If a match is made on an entity name, including the URL base at the container level, then the value is set in the server provided the read/write attribute allows the set.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
Network server information has traditionally been obtained through the use of operating systems functions and calls. By adding URL protocol code to the network server, such data may be obtained by use of a URL. In the URL, path information for the container in the server where such data resides is included. Specific server data may be retrieved, or such data may be retrieved recursively among several levels of containers. System calls and other functions may also be added to the URL path name for searching for particular data, or similar types of data through successive levels of containers. The protocol allows server administrators to access server data, in real time, from any user device in a network in which the server resides.
Description
- The instant application is a continuation of, and hereby claims priority to, pending U.S. patent application Ser. No. 12/730,000, titled “Streaming Server Administration Protocol” by inventor John Murata, which was filed on 23 Mar. 2010. The instant application further claims priority to U.S. patent application Ser. No. 09/680,991, titled “Streaming Server Administration Protocol” by inventor John Murata, which was filed on 6 Oct. 2000, which issued as U.S. Pat. No. 7,716,674 on 11 May 2010, to which parent application Ser. No. 12/730,000 also claims priority. Each of these applications is incorporated by reference.
- The present invention relates generally to protocols and more particularly to a network based administration protocol.
- Server administrators have traditionally used operating system commands, calls and functions to obtain internal server data. With these commands, the server administrator can typically display the server status, display the number of current connections and the detailed information for each connection, display the configuration options for the server, display the configuration options for each server module extension, modify the configuration options for server and module extension, display all server module extensions, display real-time statistics for the server, for example, average number of connections, what streaming applications are being selected and their frequency of selection, the current number of connections and bandwidth used, and display the entire server state for debugging and servicing of problems.
- Examples of such configuration options referred to above include, the maximum number of connections allowed, the default server directory or list of directories, the maximum or minimum buffer size, the time interval for a process or function, the time duration for a process or function, error messages, enable or disable features, a file or list of files for a feature, or a user or list of users for a feature.
- For example, based on the real-time number of connections returned by a streaming server, a web server can dynamically create URL's to different streaming servers to load balance across multiple servers or networks. In another example, based on the real-time file access returned by a streaming server, a web server providing an access page to the streaming servers can dynamically create browser URL's to allow, deny, or redirect access to different streaming files to load balance or control access to users.
- Traditional tools available to server administrators, however, require a specific command or network request for a specific data element or set or set of data elements. In most cases, additional data access requires additional commands and changes to the server and administrator software. One disadvantage of a direct mapping between command and data is the lack of the ability for data discovery and a rigid connection between a particular tools's code and the server data it can retrieve, display or process. Furthermore, these tools generally consume server resources when run. The resource allocation for these tools may disadvantageously effect the performance of other applications running on top of the server operating system. When a server is streaming data into a computer network for transmission to the client, such limitations on the performance of the streaming application may disadvantageously result in the interruption of streaming data. For example, in a streaming video application, the interruption of data may result in perceptible distortion or pausing of a video image displayed on a user device connected to the network.
- It would be desirous to provide a network software application like a streaming server which would allow server administrators to access server data from any user device in a network. It would be further desirous to provide a streaming server which would allow server administrators to access such data remotely in real time. It would be advantageous to software creators to provide a server data administration feature requiring a minimum of software changes to existing HTTP based software tools in order to gather information, change information or work with new information stored in a network software application
- It is an object of the present invention to overcome one or more disadvantages and limitations of the prior art herein above enumerated.
- It is a further object of the present invention to allow a single mechanism to add, set, delete or retrieve any required server data value.
- It is yet another object of the present invention to use a query mechanism that defines an array iterator and name lookup.
- It is still a further object of the present invention to allow for data discovery and retrieval of specific data elements.
- According to the present invention, a novel protocol is implemented in a streaming server module for real time access to network software data from any location within a computer network in which the server resides. The novel protocol supports the use of standard network software programs like web server CGIs and HTTP client software like web browsers for accessing the data from any user device connected to the network or local to the server. The internal network software data structures are modified using the invention's protocol syntax to support a connected network client software program. The protocol relies on upon the URI mechanism for specifying a container entity using a path, and HTTP 1.0 for specifying request and response mechanisms. The goal of the protocol is to remove the usual administration protocol mapping between a command and the data it references, and replace this function with a simple HTTP based command with a URI formatted data specifier
- A feature of the present invention is that the server data is obtainable remotely through the network or locally at the server. A further feature of the present invention is that the administration protocol does not require network transport support.
- Still further features of the present invention are the ability to provide within the protocol password protected access to the server data whether accessed locally or remotely and multiple simultaneous administrator requests. Another feature is that the protocol allows data discovery and retrieval with various data types, for example, character, integer and floating point.
- Yet further features of the protocol of the present invention is the ability to provide read and write permissions to the information provided by the access to the server data, and the ability to modify the server state such as session, server and preferences.
- Still further features are that the request and response for server data is formatted as an HTTP GET request and response. The response data from the server may also be HTML or XML formatted.
- Additional features of the present invention is that the protocol allows for specific data requests of server data, server side data filtering, setting of server attributes, adding, removing and setting server data elements and values, and multiple filters per request for data coherency and performance.
- These and other objects advantages and features of the present invention will become apparent to those skilled in the art from a study of the following Description of the Exemplary Preferred Embodiments when read in conjunction with the attached drawing and appended Claims.
-
FIG. 1 is a schematic block diagram of a network constructed according to the principals of the present invention. -
FIG. 2 is a flow chart of an exemplary process of the present invention. - Referring now to
FIG. 1 , there is shown acomputer network 10 constructed according to the principles of the present invention.Network 10 includes aserver 12 and aclient 14, the communication between theserver 12 and theclient 14 may be either directly connected or through anothermedium 16, which may be any of a local area network, wide area network, the Internet, or any other proprietary or public network. Each of theserver 12 andclient 14 respectively have associated therewith a computerreadable medium - With reference to
FIG. 2 , theserver 12 receives an HTTP path name, as indicated at 30. At 32, a decision is made whether an administrative module is identified in the path name. If not and the path name identifies, for example, a typical HTML page, the server would send the HTML page, as indicated at 34. If yes, as indicated at 36, theserver 12 process the novel protocol of the present invention, as described in detail herein below. After processing the HTTP path name identifying an administrative module, the administrative data is sent to theclient 14, as indicated at 38. - The novel protocol of the present invention support use of CGI's or HTTP client software to develop monitoring and administration software to obtain server data of the type particularly useful to server administrators. To implement such a protocol, abstraction from the internal server data structure of the server on which the protocol resides is required as well as changes to such internal data structure, to support the requests described in greater detail herein below.
- The novel protocol of the present invention also allows for network or local access by server administrators to internal server data. The protocol does not require network transport support. The protocol of the present invention relies upon the URI mechanism as defined by RFC2396 for specifying a container entity using a path and HTTP 1.0 RFC 1945 for specifying request and response mechanisms.
- More specifically, access to internal server data may be obtained through client software by using the familiar path name of a URL in conventional client software, wherein the path name specifies a container from which such data may be obtained. For, example, a path name may be written as URL/module/admin/, wherein module/admin/ is the container. It will become readily apparent from the description herein below that the use of the URL can retrieve data from various levels of container data. The protocol of the present invention in addition to supporting the URL path name, also supports CGI scripting at the server so that commands may be added to the path name.
- More specifically, requirements for the implementation of the novel protocol of the present invention are described herein below with respect to specific headings. For clarity and to enable those skilled in the art to practice the present invention, the syntax of the URI is also provided. Reference is made to the Drawing figures to give examples of various requests and responses using herein described protocol.
- Request Methods
- HTTP GET is the primary request method. HTTP POST can be used to perform multiple data requests.
- Session State
- The session is closed at the end of each HTTP request response.
- Evaluation of POST
- A POST Request-URI with a query parameter of command =SET is a set of server data. Body name=“value” pairs are required and evaluated as discrete sets.
- A POST Request-URI without a query parameter or a query parameter of command=GET is evaluated as a get of a data name or value. Body URL filters are not required.
- Request Header Features
- Authorization
- If-Modified-Since
- Server Data
- All data on the server is specified using an URI
- Definition of Server URL
- Administration URL references directed to the server must specify the “/qtss” base segment and the admin module “/admin”. The path names are significant for routing the request to the appropriate request handler.
- For example, http://server:port/qtss/admin, references the qtss admin module which implements the admin protocol
- URI Requests
- Always absolute references beginning with the Server URL
- rule:
- [absolute URL]?[parameters=“value(s)”]+[option=“value”]+[option=“value”]
- example:
- /qtss/admin/server/sessions?parameters=rva+snapshots=“value”
- URI Rules
- /path=absolute reference
- path=relative reference
- path/=/is defined as any container in the “path” reference
- *=iterate each element in the current location
- path/*=is defined as all elements contained in the “path” reference
- .=not supported
- ..=not supported
- ;=not supported
- ?=query options follow (“+” delimited name=“value” pairs)
- spaces and tabs=stop characters
- “”=are supported from values and required for values containing spaces and tabs.
- Path Definition
- A path represents a virtual hierarchical data structure of containers and is expressed as a URL. The path terminates with an element. The terminating element may be a container.
- Elements are arrays. If there is a single element in the array, then the following URL queries are equivalent: “path/element”, “path/element/”, “path/element/*”, and “path/element/1” are all evaluated as the same query.
- Query Options
- A URI without a ‘?’ defaults to a GET request
- example: /qtss/admin/server/sessioncount
- A URI containing a ‘?’ designator must contain a “command=thecommand” query option.
- example: /qtss/admin/server/sessioncount?command=GET
- Query options are not case sensitive. Query option values are case sensitive. Unknown query options are ignored. Query options not required by a command are ignored.
- command option:
- command=[GET|SET|DEL|ADD]
- Unknown command are reported as an error.
- command=GET←get data identified by URI. (“←”=comment)
- The GET does not require other query options
- Example: GET/qtss/admin/maxcount
- command=SET←set data identified by URI
- The command sets the element value referenced by the URL. The required query options are value=
- value checking is not performed. Conversion between the text value and the actual value is type specific.
- Example: GET/qtss/admin/maxcount?command=SET+value=5
- optional query options for the SET command
- type=←if defined then type checking of the server element type and the set type is performed. If a match of the stored type and the request type fails, an error is returned an the command fails.
- Example:
- GET/qtss/admin/maxcount?command=SET+value=5+type=SInt32
- command=DEL←delete data identified by the URI. The command deletes the element referenced by the URL. Example:
- GET/qtss/admin/maxcount?command=DEL
- command=ADD←add data identified by the URI. If the element at the end of the URL is an element the ADD performs an add to the array of elements referenced by the element name.
- Required query options are: value=and type=
- example: GET/qtss/admin/maxcount? command=ADD+value=6+type=SInt16+access=rw
- optional query options for the ADD command are: access=
- example: GET/qtss/admin/? command=ADD+value=5+name=maxcount type=SInt16+access=rw
- If the element at the end of the URL is a QTSS Object container, then an ADD performs a named element add to the container. Required query options in this case are: value=, type=and name=. Example: GET/qtss/admin/? command=ADD+value=5+name=maxcount type=SInt16
- parameter options:
- r=recurse-. walk downward in hierarchy (path?parameters=r and path/*?parameters=r are evaluated as the same query)
- v=verbose→return full path in name
- a=access→return read/write access
- t=type→return type of value
- d=debug→return debugging info with error
- c=count→return count of elements in path
- Parameters are always single characters with no delimiters. Parameter options follow the URL, e.g., [URL]?parameters=[p][p],
- example path/path?parameters=rvat
- Data Types
- Data types can be any server allowed text value. New data types can be defined and returned by the server. The data types are: Uint8, Sint8, Uint16, Sint16, Uint32, Sint32, Uint64, Sint64, Float32, Float64, Boo18, Bool16, CharArray, QTSS_Object, and void pointer. QTSS_Objects, pointers and unknown data types always convert to a host ordered hex value. The values converted are returned in hex. AN example is when adding a new attribute to the server. If the type is not known by the server, then the value returned will be a string of hex values.
- Snapshots
- A snapshot is the container of values from which an admin response is generated (the measured values at a particular point in time, as compared to the constantly changing values). There is one active snapshot per admin connection. Each request without a snapshot in the URI generates a new snapshot. There is only one current snapshot per request. Each new snapshot invalidates the previous per admin connection snapshot. A snapshot is a hierarchy of containers specifying the type, name, value and read/write attribute of values copied from the server's internal structures using the module API (Application Program Interface)
- Snapshots are always complete copies of the referenced resources, however, the returned data can be filtered by specifying the desired fields in the body of a request.
- Response appears as SNAPSHOT:Value
- Request Definitions
- A GET without a snapshot query value is a request which automatically makes a new snapshot. If the snapshot is not returned by the server, then snapshots are not supported.
- A POST contains the default set of objects in the URL. The POST body can contain multiple sub URL's performing multiple SET, GET or DEL command operations on the set of data represented by the default URL.
- Query Options
- Options appear at the end of the URI
- example: path segment/path segment?option=“value”, option=“value”
- URI POST Filters
- Filters specify a subset of data to be returned on each request. Multiple filters are evaluated in order with each result placed in the response.
- Once a filter accepts a value, it is returned.
- Order of appearance when recursing is breadth first. Filter defined attributes replace any previous attributes settings for each filter response. The request URI is the default filter. New filters override the parameters defined by the request URI.
- Response Data
- All entity references follow the form [NAME=VALUE]; [attribute=“value”],[attribute=“value”]
- NAME=VALUE
- NAME=VALUE;attribute=“value”
- NAME=VALUE;attribute=“value”;attribute=“value”
- All container references follow the form [NAME/];[attribute=“value”],[attribute=“value”]
- NAME/NAME/;attribute=“value”
- NAME/;attribute=“value”;attribute=“value”
- Root Value
- /admin
- Errors in Response
- The error state for the request is always reported with each response at the end of the data.
- Error:(0),- no error
- Error: (404)←data not found
- Setting Entity values
- When changing server values, the entities' name and their values are located in the request body. If a match is made on an entity name, including the URL base at the container level, then the value is set in the server provided the read/write attribute allows the set.
- base=base/container
- name=value
- /base/container/name=“value”
- There has been described herein above a novel protocol for obtaining administrative server data using client software which transmits a URI to the server. Those skilled in the art may now make numerous uses of and departures from the exemplary preferred embodiments disclosed herein without departing from the inventive concepts of the present invention. Accordingly, the present invention is to be defined solely by the scope of the appended Claims.
Claims (20)
1. A method for obtaining internal server data from a server, comprising:
in the server, performing operations for:
determining whether a path name received in a request from a client includes an identity of a container of the server, the container comprising data that includes types, names, and values;
when the path name does not include the identity of a container:
transmitting a corresponding hypertext markup language (HTML) page to the client; and
when the path name includes the identity of a container:
processing the path name to retrieve a snapshot of the container, the snapshot representing a current state of the data in the container;
generating, from the snapshot, a response; and
transmitting the response to the client.
2. The method of claim 1 , further comprising:
in the server, performing operations for:
modifying information included in the container based on the path name.
3. The method of claim 2 , wherein modifying information included in the container based on the path name comprises:
modifying the information based on at least one of a command and a value included in the path name.
4. The method of claim 1 , wherein the path name indicates a virtual hierarchical data structure of containers.
5. The method of claim 1 , wherein the snapshot comprises read/write attributes of information included in the container.
6. The method of claim 1 , further comprising:
in the server, performing operations for:
filtering data from snapshot based on the path name and one or more filters in the request to generate a subset of data from the snapshot;
wherein generating, from the snapshot, the response comprises generating the response using the subset of data.
7. The method of claim 1 , wherein the path name is an HTTP path name.
8. The method of claim 1 , wherein a new snapshot is generated when no snapshot is included in the path name of the request, the new snapshot invalidating a previous snapshot.
9. A non-transitory computer-readable storage medium storing instructions that, when executed by a server computer, cause the server computer to perform a method for obtaining internal server data from the server computer, the method comprising:
determining whether a path name received in a request from a client includes an identity of a container of the server, the container comprising data that includes types, names, and values;
when the path name does not include the identity of a container:
transmitting a corresponding hypertext markup language (HTML) page to the client; and
when the path name includes the identity of a container:
processing the path name to retrieve a snapshot of the container, the snapshot representing a current state of the data in the container;
generating, from the snapshot, a response; and
transmitting the response to the client.
10. The computer-readable storage medium of claim 9 , wherein the method further comprises:
modifying information included in the container based on the path name.
11. The computer-readable storage medium of claim 10 , wherein modifying information included in the container based on the path name comprises:
modifying the information based on at least one of a command and a value included in the path name.
12. The computer-readable storage medium of claim 9 , wherein the path name indicates a virtual hierarchical data structure of containers.
13. The computer-readable storage medium of claim 9 , wherein the snapshot comprises read/write attributes of information included in the container.
14. The computer-readable storage medium of claim 9 , wherein the method further comprises:
filtering data from snapshot based on the path name and one or more filters in the request to generate a subset of data from the snapshot;
wherein generating, from the snapshot, the response comprises generating the response using the subset of data.
15. The computer-readable storage medium of claim 9 , wherein the path name is an HTTP path name.
16. The computer-readable storage medium of claim 9 , wherein a new snapshot is generated when no snapshot is included in the path name of the request, the new snapshot invalidating a previous snapshot.
17. A server computer that provides internal server data, comprising:
a processor; and
a network interface;
wherein the processor and the network interface perform operations for:
determining whether a path name received in a request from a client includes an identity of a container of the server, the container comprising data that includes types, names, and values;
when the path name does not include the identity of a container:
transmitting a corresponding hypertext markup language (HTML) page to the client; and
when the path name includes the identity of a container:
processing the path name to retrieve a snapshot of the container, the snapshot representing a current state of the data in the container;
generating, from the snapshot, a response; and
transmitting the response to the client.
18. The server computer of claim 17 , wherein the processor performs operations for modifying information included in the container based on the path name.
19. The server computer of claim 18 , wherein the processor performs the operations for modifying the information based on a command and a value included in the path name.
20. The server computer of claim 17 , wherein the path name indicates a virtual hierarchical data structure of containers.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/275,313 US20140244735A1 (en) | 2000-10-06 | 2014-05-12 | Streaming server administration protocol |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/680,991 US7716674B1 (en) | 2000-10-06 | 2000-10-06 | Streaming server administration protocol |
US12/730,000 US8732731B2 (en) | 2000-10-06 | 2010-03-23 | Streaming server administration protocol |
US14/275,313 US20140244735A1 (en) | 2000-10-06 | 2014-05-12 | Streaming server administration protocol |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/730,000 Continuation US8732731B2 (en) | 2000-10-06 | 2010-03-23 | Streaming server administration protocol |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140244735A1 true US20140244735A1 (en) | 2014-08-28 |
Family
ID=24733324
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/680,991 Expired - Lifetime US7716674B1 (en) | 2000-10-06 | 2000-10-06 | Streaming server administration protocol |
US12/730,000 Expired - Fee Related US8732731B2 (en) | 2000-10-06 | 2010-03-23 | Streaming server administration protocol |
US14/275,313 Abandoned US20140244735A1 (en) | 2000-10-06 | 2014-05-12 | Streaming server administration protocol |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/680,991 Expired - Lifetime US7716674B1 (en) | 2000-10-06 | 2000-10-06 | Streaming server administration protocol |
US12/730,000 Expired - Fee Related US8732731B2 (en) | 2000-10-06 | 2010-03-23 | Streaming server administration protocol |
Country Status (3)
Country | Link |
---|---|
US (3) | US7716674B1 (en) |
AU (1) | AU2001289139A1 (en) |
WO (1) | WO2002032056A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160147427A1 (en) * | 2013-06-26 | 2016-05-26 | Hewlett-Packard Development Company, L.P. | Thin client computing device taskbar and widgets |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8281401B2 (en) * | 2005-01-25 | 2012-10-02 | Whitehat Security, Inc. | System for detecting vulnerabilities in web applications using client-side application interfaces |
CN101273337B (en) * | 2005-10-06 | 2010-10-06 | 三菱电机株式会社 | Terminal device, server device, and command device |
US20090204578A1 (en) * | 2008-02-12 | 2009-08-13 | Microsoft Corporation | Targeted queries using an oma dm protocol |
US8543676B2 (en) * | 2009-06-16 | 2013-09-24 | International Business Machines Corporation | Delegated resource use in a content based routing environment |
US8984616B2 (en) | 2010-12-08 | 2015-03-17 | International Business Machines Corporation | Efficient routing for reverse proxies and content-based routers |
US10298668B2 (en) | 2014-03-24 | 2019-05-21 | Square Enix Co., Ltd. | Interactive system, terminal apparatus, server apparatus, control method, program, and recording medium |
US10516733B2 (en) | 2014-11-25 | 2019-12-24 | Auth0, Inc. | Multi-tenancy via code encapsulated in server requests |
US10452757B2 (en) * | 2014-11-25 | 2019-10-22 | Oracle International Corporation | Persistent user personalization |
US10116725B2 (en) * | 2016-05-27 | 2018-10-30 | Intuit Inc. | Processing data retrieval requests in a graph projection of an application programming interfaces (API) |
US9753744B1 (en) * | 2016-05-27 | 2017-09-05 | Intuit Inc. | Defining application programming interfaces (APIS) using object schemas |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5574903A (en) * | 1994-05-13 | 1996-11-12 | Apple Computer, Inc. | Method and apparatus for handling request regarding information stored in a file system |
US5673322A (en) * | 1996-03-22 | 1997-09-30 | Bell Communications Research, Inc. | System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks |
US5793966A (en) * | 1995-12-01 | 1998-08-11 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for creation and maintenance of online services |
US6000033A (en) * | 1997-11-26 | 1999-12-07 | International Business Machines Corporation | Password control via the web |
US5999943A (en) * | 1997-10-31 | 1999-12-07 | Oracle Corporation | Lob locators |
US6061741A (en) * | 1997-05-28 | 2000-05-09 | International Business Machines Corporation | Method and apparatus for synchronization of connectionless applications across a network by using simple encryption tokens |
US6557024B1 (en) * | 1998-09-03 | 2003-04-29 | Fuji Xerox Co., Ltd. | Distributed file processing with context unit configured to judge the validity of the process result on the basis of the name of the raw file and the name of the executed procedure |
US7209953B2 (en) * | 2002-12-12 | 2007-04-24 | Mark Brooks | E-mail system using attachment identifier generated at issuer device for retrieving appropriate file version from e-mail's issuer |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5692194A (en) * | 1993-05-24 | 1997-11-25 | Hughes Aircraft Company | Sequential information integration service for automatically transferring a most recent data entity between a plurality of program modules and a storage in a computer |
US5657446A (en) * | 1994-11-14 | 1997-08-12 | Mitel Corporation | Local area communications server |
US5857102A (en) * | 1995-03-14 | 1999-01-05 | Sun Microsystems, Inc. | System and method for determining and manipulating configuration information of servers in a distributed object environment |
US5732219A (en) * | 1995-03-17 | 1998-03-24 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for remote editing of computer files |
US5826269A (en) * | 1995-06-21 | 1998-10-20 | Microsoft Corporation | Electronic mail interface for a network server |
US5944781A (en) * | 1996-05-30 | 1999-08-31 | Sun Microsystems, Inc. | Persistent executable object system and method |
US5768515A (en) * | 1996-07-08 | 1998-06-16 | Microsoft Corporation | Method for generating and storing two segments of HTTP message headers with different lifetimes and combining them to form a single response header |
JP3488347B2 (en) * | 1996-08-29 | 2004-01-19 | 株式会社日立製作所 | Automatic address distribution system and address distribution server |
US5987504A (en) * | 1996-12-31 | 1999-11-16 | Intel Corporation | Method and apparatus for delivering data |
US5875296A (en) * | 1997-01-28 | 1999-02-23 | International Business Machines Corporation | Distributed file system web server user authentication with cookies |
FI115566B (en) * | 1997-06-02 | 2005-05-31 | Ericsson Telefon Ab L M | Method and arrangement for browsing |
US6263387B1 (en) * | 1997-10-01 | 2001-07-17 | Micron Electronics, Inc. | System for automatically configuring a server after hot add of a device |
US6061678A (en) * | 1997-10-31 | 2000-05-09 | Oracle Corporation | Approach for managing access to large objects in database systems using large object indexes |
US6061692A (en) * | 1997-11-04 | 2000-05-09 | Microsoft Corporation | System and method for administering a meta database as an integral component of an information server |
US6094679A (en) * | 1998-01-16 | 2000-07-25 | Microsoft Corporation | Distribution of software in a computer network environment |
US6038598A (en) * | 1998-02-23 | 2000-03-14 | Intel Corporation | Method of providing one of a plurality of web pages mapped to a single uniform resource locator (URL) based on evaluation of a condition |
JP3966598B2 (en) * | 1998-03-04 | 2007-08-29 | 富士通株式会社 | Server selection system |
US6212565B1 (en) * | 1998-08-26 | 2001-04-03 | Sun Microsystems, Inc. | Apparatus and method for improving performance of proxy server arrays that use persistent connections |
US6327608B1 (en) * | 1998-09-25 | 2001-12-04 | Microsoft Corporation | Server administration tool using remote file browser |
US6308205B1 (en) | 1998-10-22 | 2001-10-23 | Canon Kabushiki Kaisha | Browser-based network management allowing administrators to use web browser on user's workstation to view and update configuration of network devices |
US6687878B1 (en) | 1999-03-15 | 2004-02-03 | Real Time Image Ltd. | Synchronizing/updating local client notes with annotations previously made by other clients in a notes database |
US6629127B1 (en) * | 1999-07-26 | 2003-09-30 | Microsoft Corporation | Methods and systems for processing HTTP requests |
US6587959B1 (en) * | 1999-07-28 | 2003-07-01 | Emc Corporation | System and method for addressing scheme for use on clusters |
US6622170B1 (en) * | 1999-09-10 | 2003-09-16 | International Business Machines Corporation | System and method for DEN/LDAP client database access with a backoff capability |
US8028049B1 (en) * | 2000-02-01 | 2011-09-27 | Peer Intellectual Property Inc. | Apparatus and method for web-based tool management |
-
2000
- 2000-10-06 US US09/680,991 patent/US7716674B1/en not_active Expired - Lifetime
-
2001
- 2001-09-18 AU AU2001289139A patent/AU2001289139A1/en not_active Abandoned
- 2001-09-18 WO PCT/US2001/029377 patent/WO2002032056A2/en active Application Filing
-
2010
- 2010-03-23 US US12/730,000 patent/US8732731B2/en not_active Expired - Fee Related
-
2014
- 2014-05-12 US US14/275,313 patent/US20140244735A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5574903A (en) * | 1994-05-13 | 1996-11-12 | Apple Computer, Inc. | Method and apparatus for handling request regarding information stored in a file system |
US5793966A (en) * | 1995-12-01 | 1998-08-11 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for creation and maintenance of online services |
US5673322A (en) * | 1996-03-22 | 1997-09-30 | Bell Communications Research, Inc. | System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks |
US6061741A (en) * | 1997-05-28 | 2000-05-09 | International Business Machines Corporation | Method and apparatus for synchronization of connectionless applications across a network by using simple encryption tokens |
US5999943A (en) * | 1997-10-31 | 1999-12-07 | Oracle Corporation | Lob locators |
US6000033A (en) * | 1997-11-26 | 1999-12-07 | International Business Machines Corporation | Password control via the web |
US6557024B1 (en) * | 1998-09-03 | 2003-04-29 | Fuji Xerox Co., Ltd. | Distributed file processing with context unit configured to judge the validity of the process result on the basis of the name of the raw file and the name of the executed procedure |
US7209953B2 (en) * | 2002-12-12 | 2007-04-24 | Mark Brooks | E-mail system using attachment identifier generated at issuer device for retrieving appropriate file version from e-mail's issuer |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160147427A1 (en) * | 2013-06-26 | 2016-05-26 | Hewlett-Packard Development Company, L.P. | Thin client computing device taskbar and widgets |
Also Published As
Publication number | Publication date |
---|---|
WO2002032056A3 (en) | 2002-11-21 |
WO2002032056A2 (en) | 2002-04-18 |
US7716674B1 (en) | 2010-05-11 |
US8732731B2 (en) | 2014-05-20 |
US20100299406A1 (en) | 2010-11-25 |
AU2001289139A1 (en) | 2002-04-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8732731B2 (en) | Streaming server administration protocol | |
US6954778B2 (en) | System and method for accessing directory service via an HTTP URL | |
US6542515B1 (en) | Profile service | |
US6920455B1 (en) | Mechanism and method for managing service-specified data in a profile service | |
US6317748B1 (en) | Management information to object mapping and correlator | |
US5878219A (en) | System for integrating access to proprietary and internet resources | |
US5987513A (en) | Network management using browser-based technology | |
US6253254B1 (en) | Hyper media object management | |
US6256031B1 (en) | Integration of physical and virtual namespace | |
KR101176757B1 (en) | Service discovery and publication | |
US7016959B2 (en) | Self service single sign on management system allowing user to amend user directory to include user chosen resource name and resource security data | |
US6859798B1 (en) | Intelligence server system | |
US7613815B1 (en) | Method and apparatus for customized logging in a network cache | |
US8150863B2 (en) | Methods, systems and computer program products for monitoring changes to objects on a computer system using information models and baselines | |
US7165104B2 (en) | Method and apparatus for managing computing devices on a network | |
US7174349B1 (en) | HTML/DHTML web interface system and method | |
US8788528B2 (en) | Filtering cached content based on embedded URLs | |
US20030208533A1 (en) | Method and apparatus for managing web services within a computer network system | |
US20020107872A1 (en) | Object manager for common information model | |
KR20050115907A (en) | Relational model for management information in network devices | |
US6446117B1 (en) | Apparatus and method for saving session variables on the server side of an on-line data base management system | |
US8380806B2 (en) | System and method for absolute path discovery by a storage virtualization system | |
US11507591B2 (en) | Methods, systems, and computer readable mediums for command engine execution | |
US6801911B1 (en) | Data processing system and method for accessing files | |
US7272836B1 (en) | Method and apparatus for bridging service for standard object identifier based protocols |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |