WO1998004971A1 - Procede et systeme de mise en application d'un protocole generalise sur des connexions de communications client/serveur - Google Patents

Procede et systeme de mise en application d'un protocole generalise sur des connexions de communications client/serveur Download PDF

Info

Publication number
WO1998004971A1
WO1998004971A1 PCT/US1997/012214 US9712214W WO9804971A1 WO 1998004971 A1 WO1998004971 A1 WO 1998004971A1 US 9712214 W US9712214 W US 9712214W WO 9804971 A1 WO9804971 A1 WO 9804971A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
connection
server
http
application
Prior art date
Application number
PCT/US1997/012214
Other languages
English (en)
Inventor
Paul B. Painter
John W. Hardin
Original Assignee
Tradewave Corporation
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
Application filed by Tradewave Corporation filed Critical Tradewave Corporation
Priority to AU37270/97A priority Critical patent/AU3727097A/en
Publication of WO1998004971A1 publication Critical patent/WO1998004971A1/fr

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/327—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the session layer [OSI layer 5]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/328—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the presentation layer [OSI layer 6]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to computer networks having enhanced and/or extended client server communications. More particularly, the present invention is characterized by an application-independent, object-oriented connection manager for processing client/server connections (communications sessions) between client
  • Client/server communications between client computers and server computers are commonly established by the interaction of an application program running on the client and a corresponding application program running on the server.
  • the client/server model is the conventional model governing the transfer of data between application programs on a computer network. According to this model, the high-level protocols for reading and writing data between a first computer (the client) and a second computer (the server) are embedded in the application software running on the client and server, respectively. Prior to the transfer of data, a communications session must be
  • Such a communication session is established according to a number of "layers" of protocols.
  • layers of protocols.
  • physical connectivity between the client machine and the server machine is established and maintained. For example, the
  • Ethernet CSMA/CD protocol is a common data link layer protocol governing the orderly transmission of packets of data between a client and server.
  • Higher-level protocols such as the TCP/IP and XNS transport layer protocols, govern the assembly of data into messages and the uniform addressing of various computers on the network. Due
  • Still higher level protocols govern the interoperability of particular client/server applications such as file transfer, remote file access, electronic mail, etc.
  • client/server applications such as file transfer, remote file access, electronic mail, etc.
  • client/server applications such as file transfer, remote file access, electronic mail, etc.
  • client/server applications such as file transfer, remote file access, electronic mail, etc.
  • Examples of such applications include Internet-based applications, where use of a file transfer protocol permits the transfer of files from ftp server sites (ftp://xxx.xxx); a different
  • client server application is typically specially adapted at the source code level to implement these protocols.
  • the task of setting up a client/server communications session employing the desired protocol is typically accomplished by application-specific code developed by the application vendor for permitting the application program to be run on a client and communicate with a server on the network using higher-level protocols such as ftp, http, or gss-http.
  • Protocols for establishing secure client/server connections have conventionally been handled in the foregoing manner For example, Internet Web-based client applications often employ software security packages to establish secure client/server communications, but only after the application software has been invasively modified at
  • the application program at the server must "know" that a security protocol is being employed, and the application program must be specially adapted to work with the security protocol
  • WebCrusader software allows users to securely access distributed applications using standard, off-the-shelf Web browsers installed on desktop client systems This product is purported to establish a secure session between an off-the-shelf Web client application and a Web server using the DCE (Distributed Computing Environment) RPC (Remote Procedure Calls) protocol
  • WebCrusader comprises an application- independent "Connect Client” function resident on the client machine which interacts with the client application, usually a Web browser
  • the Connect Client in conjunction with a corresponding "Connect Server” function resident on the server, uses the DCE RPCs to forward requests from the Web browser to the server
  • the Connect Server function receives these requests, performs security checks, fetches the requested document, and uses DCE RPCs to send the document securely back to the Connect Client for forwarding on to the Web browser.
  • the Connect Client acts as a "proxy,” intercepting document requests from the Web browser and determining whether a
  • the Connect Client uses DCE RPCs to forward the request to the Connect Server resident on the secure server. If the URL contains a non-secure address, the Connect Client forwards the request to the appropriate standard Web server using http.
  • the WebCrusader transparently performs the security functions of authentication, authorization and encryption between a client application and a server using DCE.
  • the software is strictly limited to the RPC protocol between client and server, however, and is not stream-based.
  • connection manager suitable for use with any higher-level protocol, such as ftp, http, DCE and gss-http without having to convert to RPC call sequences. It is desired that such a connection manager tansparently set up and manage both secure and non-secure client/server
  • a client machine and a server machine in a computer system wherein the client and server include a connection manager for establishing communications sessions using higher-level protocols such as http, ftp, or gss-http.
  • the client machine may be any computer capable of running a client application, and will typically include a memory device such as a hard disk drive for storing the client application; a processor for executing the client application; and means for handling input/output (I/O).
  • connection manager typically comprises a client component running on the client machine, and a server component running on the server machine. These dual components of the connection manager together manage a series of connections between a client application and a server application.
  • the client component receives
  • the client aspect and the server aspect are thus in part mirror images of each other, and they function jointly as an "agent" of the communications between the client and the server.
  • connection manager can be run on a machine other than the client machine (on which the client application runs) or the server machine (on which the server application runs).
  • a client machine running a client application may be interoperable with a separate machine running the connection manager, which may then apply the appropriate protocols and enhancements to the connection between the client application and a distant server application.
  • the connection manager handles requests from a client application using an object-oriented approach to process (set up and manage) the communications session
  • connection manager is "object-oriented" in that it uses various discriminators determinable from the client or server communication content (e.g., protocol, client or server address, data type, etc.) to evaluate which type of communications connection, or class, is called for.
  • client or server communication content e.g., protocol, client or server address, data type, etc.
  • connection manager can "type" the object and call on the communications methods corresponding to that class of connection when setting up the communications session and carrying out the communications protocols between the client and the server.
  • connection manager is application-independent.
  • client/server applications may be used with the connection manager, and these applications need not be adapted for use with the connection manager.
  • the connection manager receives ordinary requests originated
  • connection manager uses the content of those requests to set up and manage a communications session between the client and the server. Requests from a wide variety of applications and for a wide variety of classes of connections can be accommodated by the connection manager in this manner.
  • the connection manager maintains one or more active "listener" objects that await requests for connections of particular types.
  • the connection manager associates with that connection the group of communications methods for connections of that class.
  • a client/server connection manager which is non-invasive with respect to the various applications with
  • connection manager receives high-level, connection-specific requests from the client.
  • the connection manager uses these requests to determine the lower-level protocols required for creating the desired type of connection, such as a
  • connection manager employs client-resident portions and server-resident portions to manage the communications and supply the lower-level protocols without any modifications to the client application or the server application at the source code level.
  • FIG. 1A is a simple block diagram representation of a client/server connection manager according to the present invention.
  • FIG. 1B is a block diagram of a client/server connection manager separated into its client and server components in a distributed computing environment.
  • FIG. 2A is a functional design diagram of the client component of a connection manager with active listener objects which determine when connections of various
  • FIG. 2B is a functional design diagram showing a single listener object associated with a single class of methods for an http connection.
  • FIG. 3A is a flow chart of the functioning of a client/server connection manager in the computer system according to the present invention.
  • FIG. 3B is a more detailed textual outline of the flow chart shown in FIG. 3A.
  • FIG. 4A is a communications activity flow diagram showing the establishment of a communications session between a client and a server using only the client component of a connection manager.
  • FIG. 4B is a textual outline of the communications activity shown in FIG. 4A.
  • FIG. 5A is a communications activity flow diagram showing the establishment of a secure communications session between a client and a server using both the client component and a server component of a connection manager.
  • FIG. 5B is a textual outline of the secure communications activity shown in FIG. 5A.
  • FIG. 1A wherein a client machine 2 and a server machine 4 are interposed by connection manager 6.
  • Client machine 2 may have resident thereon one or more client applications 3, and these applications will typically interact with one or more server applications 5 to obtain data, files, graphics, etc. from the various servers.
  • server machine 4 may be a server for one or more of ftp, http, or gopher programs on the Internet, or it may be an electronic mail server or other server on a
  • connection manager 6 in its simplest form resides on client machine 2 and manages the connections between the various client applications 3 and their target
  • Connection manager 6 sets up and manages these client/server connections using an object-oriented approach to determine, based on the type of connection sought by the client application 3 or the server application 5, the appropriate class of communications methods to apply to the connection so that input/output (I/O) between the client and server is processed seamlessly and transparently.
  • object-oriented approach of connection manager 6 is described more fully below with
  • connection manager 6 is shown to comprise client and server components where the client machine 2 and server machine 4 communicate at the application level over a network 8. Those components are designated connection manager/client (CM/C) 10 and connection manager/server (CM/S) 12, respectively.
  • CM/C 10 typically receives from the various client applications 3 certain connection requests destined for server applications 5.
  • CM/C 10 types the object, or connection sought, according to the content of the request from client application 3.
  • CM/C 10 and CM/S 12 then cooperate to establish the requested type of connection, applying the appropriate higher level protocols through the collection of methods specific to the
  • client application 3 requests a secure connection
  • CM/C 10 and CM/S 12 invoke the communications methods
  • server application 5 may be aware that the gss-http protocols are being implemented by
  • connection manager 6 Once a connection is established by the components of connection manager 6,
  • CM/C 10 I/O between client application 3 and server machine 4 is dispatched by CM/C 10 and
  • CM/S 12 in a way that is transparent to the client and server.
  • CM/C 10 invokes the
  • CM/C 10 interacts with client application 3 as if CM/C 10 were
  • server application 5 interacts with CM/S 12 in the
  • server application 5 would ordinarily interact with a client application.
  • connection manager 6 is thus transparent to client application 3 and server application 5, which require no special knowledge that the components of connection manager 6 are
  • FIG. 2A representational ly shows a plurality of logical connections established between various client applications 3' and 3" and their target server applications via a computer network.
  • CM/C 10 is preferably provided with an
  • intializer 30 for setting up a plurality of listener objects 16.
  • Listener objects 16 are tailored, through their association with connection classes 31, to detect a request for a particular type of connection from client applications 3" and 3", wherein each connection class 31 defines a collection of communications methods that implement
  • CM/C 10 When CM/C 10 accepts a connection from a client application 3' or 3", CM/C 10 associates with that connection the communications methods corresponding to that type of connection. When CM/C 10 accepts a connection request from client application 3' or 3",
  • CM/C 10 creates a connection object 24 for http connection 18, a connection object 26 for http connection 20, or connection object 28 for gss-http connection 22.
  • Connection objects 24, 26 and 28 are specialized by their respective connection classes 31 to handle connections of particular types.
  • the connection objects have pointers to the actual client and server connections, pointers to specific methods of connection classes 31, and other information allowing them to be managed by CM/C 10. For example, the
  • connection class's Init method sets connection object 24's read, write, exception, and deinit methods to http Read, http_Write, http_Exception, and http_Dein ⁇ t, respectively.
  • Event manager 14 calls the connection class methods for each connection object in order to process I/O events and apply enhancements to the protocols for each connection, e.g., adding security to http.
  • CM/S 12 is preferably designed to mirror the operation of CM/C 10 and may be designed similarly to accept communications requests on behalf of server application 5 and receive communications from the server. For simple connections such as http
  • connection 18 where data is written to and from CM/C 10 without the need for enhanced protocols such as security protocols, CM/S 12 may not be active on the server side, and connection manager 6 may then be considered to comprise only CM/C 10, which connects directly to server application 5.
  • FIG. 2A shows the establishment of three different types of connections by CM/C
  • connection 18 there is shown representationally a logical, non-secure http connection 18 between a client application 3' and a server application 5 (not shown). This connection typifies the
  • non-secure Internet communications between a client and server are also shown.
  • http connection 20 and secure gss-http connection 22, which employs the gss-http protocol.
  • CM/C 10 cooperates with CM/S 12 (not shown) to set up each connection on appropriate ports of server machine 4.
  • CM/S 12 (not shown) to set up each connection on appropriate ports of server machine 4.
  • http connection 18 and http connection 20 are typically set up on non-secure ports 80, while secure gss-http connection 22 is set up on secure server port 488 according to current standards.
  • connection objects 24, 26, and 28 which are associated with the methods for the http class, http class, and gss-http class of connection, respectively.
  • the http read method is invoked any time input data from either the client application 3 or
  • FIG. 2A may be implemented in any of a variety of ways, including subroutines (both statically and dynamically linked), executing local applications, remote procedure calls, Active-X and Java. Statically and dynamically linked subroutines have proven to be an acceptable means for implementing these methods.
  • FIG. 2B there is shown a functional design diagram of CM/C
  • Connection class 31' defines the class of http methods specific to the http connection class.
  • Listener object 16' receives a connection request on http connection 18.
  • CM/C 10 accepts the connection request and creates connection object 24, which has pointers to the http read method 60', write method 66', connect method 64' and exception method 65.
  • CM/C 10 also associates connection object 24 with the http methods of connection class 31'.
  • Event manager 14 makes calls to these methods to process the I/O on http connection 18. I/O events
  • process read routine 48 may originate from either the client or the server. Processing of these read and write events is handled by event manager 14 via process read routine 48 and process write routine 50, which make the appropriate calls to the methods associated with the connection object.
  • connection manager 6 which preferably has basic functions provided by an initialization routine 30, an event processing routine 32, and a quit routine 34.
  • Initialization routine 30 is executed once upon startup, and includes steps preliminary to establishing
  • connection manager 6 initializations specific to the platform on which connection manager 6 is installed are carried out.
  • the various program modules of connection manager 6 are initialized in step 38.
  • step 40 The appropriate methods for use with each connection class are initialized in step 42 and the listener objects 16 (FIG. 2A) are created in this step.
  • Event processing routine 32 processes I/O events, and these are preferably processed according to a process read step 48, a process write step 50, and a process exception step 52 for handling error conditions on the connection.
  • a read request is examined to determine whether it originated from the client or the server. If the read request originated from the client, step 56 determines whether it is a request to read data from the client or instead a request to accept a connection from the client.
  • Read requests originating from the server likewise invoke read method 60, which occurs when data is to be read from the server and written to the client.
  • step 63 determines whether it is a request to write data to the server or instead a signal that a server connection request previously issued has completed. Requests to write data invoke write method 66. Write requests destined for the client likewise invoke write method 66, which occurs when data is to be written to the client.
  • Event processing routine 32 may handle events other than I/O events. These include user events, such as an indication from the user that he wants connection
  • manager 6 to exit. They may also include programmatic events (e.g., another program wants connection manager 6 to exit), and so on.
  • CM/C 10 and CM/S 12 typically run respectively on client machine 2 and server machine 4, with each component handling both read and write requests from the client
  • quit routine 34 carries out step 68 to delete any active connection objects (which closes all open connections) and step 70 to deinitialize the classes of connections previously initialized in step 40.
  • FIG. 3B shows in outline form the various steps of FIG. 3A.
  • Example A Unsecure Web Connection (http) Referring to FIG. 4A, there is shown an activity flow diagram for a simple, non-
  • connection manager 6 secure client/server connection which is set up and managed by connection manager 6.
  • an http class connection is established on the Internet; client application 3 is therefore presumed to be a Web browser and server machine 4 is presumed to be a Web server. Because no higher-level network protocols (such as security protocols) are required, connection manager 6 resides only on the client
  • connection manager 6 Prior to the initiation of the activities shown in FIG. 4A, it is presumed that connection manager 6 has been initialized and that at least one listener object 16 (FIG. 2) of the http class is active.
  • connection manager 6 For http-class connections is now described.
  • client application 3 Web browser
  • URL Universal Resource Locator
  • client application 3 in step 101 attempts to open a connection to CM/C 10, which client application 3 treats as a server application 5.
  • Connection manager 6 which has at least one active http listener object 16' (FIG. 2A), accepts the connection and
  • client application 3 invokes the Init method associated with the accepting connection object (in this case, http nit).
  • client application 3 interacts with connection manager 6 as if it were the server; thus client application 3 now treats the connection as having been established with server application 5.
  • client application 3 writes an http request, such as:
  • connection manager 6 reads this request using the read method for http. After successfully reading the request line, the http class parses the specified URL to determine if it is valid. If the URL is not valid, then connection manager 6 signals an error. After successfully parsing the specified URL, the http class read method next reads the http header lines.
  • connection manager 6 cooperates with the server to establish a connection using the connect methods (steps 106-108), and subsequently invokes the http write methods to write the client request to server machine 4 (step 109).
  • server reads this client request (step 110), it writes a response (step 111).
  • this response consists of a status line, a header, and the body of the response, e.g.: HTTP/1.0 200 OK[CR/LF]
  • connection manager 6 Like the client
  • connection manager 6 the server's communication through connection manager 6 is transparent
  • connection manager 6 is anything other than an http
  • connection manager 6 Once connection manager 6 has received the response from the server, it writes
  • Client application 3 then reads the response to the client application 3 (step 113).
  • connection manager 6
  • FIG. 4B the activities in this http example of FIG. 4A are shown in outline form in FIG. 4B.
  • FIG. 5A there is shown an activity flow diagram for a secure gss-
  • connection manager 6 components of connection manager 6, namely CM/C 10 and CM/S 12. As in Example
  • client application 3 is presumed to be a Web browser and server machine 4 is
  • CM/C 10 and CM/S 12 Prior to the initiation of the activities shown in FIG. 5A, it is presumed that CM/C 10 and CM/S 12 have been initialized and that at least one
  • listener object 16 (FIG. 2A) of the http class is active on each of CM/C 10 and CM/S 12.
  • CM/C 10 and CM/S 12 for secure gss-http connections is now described.
  • client application 3 Web browser
  • step 201 indication in step 201 that he desires secure communications with a server.
  • client application 3 attempts to open a connection with CM/C 10 (step 202) and CM/C 10 accepts the connection (step 203). The client may then write a request to
  • CM/C 10 such as:
  • the http read method observes the content of the request and determines that a gss-http secure connection is desired. Thus, the gss connect method will be set as the connect method associated with connection object 24 in FIG. 2B.
  • the http read method opens a connection to the server (steps 206-208).
  • CM/C 10 then cooperates with CM/S 12 to establish a connection by invoking the connection object's connect method (in this case, gss_Connect), which performs security context negotiation prior to the transfer of any secure data (steps 209-216).
  • the server application 5 (Web server) receives no requests and takes no part in the connection set-up until after CM/C 10 and CM/S 12 have successfully negotiated the secure connection.
  • CM/C 10 Upon completion of the security context negotiation between CM/C 10 and CM/S 12, http write methods including security protocols are invoked by CM/C 10 to send the client request securely to CM/S 12. Operating in mirror image fashion, CM/S 12 reads the client request in step 218. Thereafter, in steps 219 through 225, CM/S 12 interacts
  • CM/S 12 in FIG. 5A The sample response written to CM/S 12 in FIG. 5A is:
  • the server response may be securely written to and read by CM/C
  • connection manager 6 After writing the response to the client (step 229) for display to the user (step 230), the remainder of the connections are then closed, first by CM/C 10 (step 231), then by client application 3 (step 232).
  • client and server components of connection manager 6 established a secure gss-http connection between the client and server by interacting with client and server in a way that transparently mimics direct interaction between client and server.
  • the particular methods implementing the gss class connection in Example B are

Landscapes

  • Engineering & Computer Science (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

L'invention a pour objet un système dans lequel un gestionnaire de connexion (6) client/serveur intervient pour mettre en application des protocoles de communications entre un client (3) et un serveur (5) d'une manière transparente, autonome et sans effraction. Le gestionnaire de connexion (6) est constitué d'une composante client (3) se trouvant normalement sur la machine (2) du client et d'une composante serveur (5) résidant normalement sur la machine (4) du serveur. La composante client (3) accepte les demandes de connexions émanant des clients et établit ces connexions en collaboration avec la composante serveur (5) du gestionnaire de connexion. Le gestionnaire de connexion (6) identifie le type de connexion demandé (par exemple, ftp, http, gss-http) sur la base d'éléments tels que le contenu de la demande et appelle les procédés propres au type de connexion requis. Il peut ainsi mettre en application des protocoles de plus haut niveau, tels que des protocoles de sécurité, pour assurer la connexion de façon transparente aussi bien pour le client (3) que pour le serveur (5).
PCT/US1997/012214 1996-07-25 1997-07-25 Procede et systeme de mise en application d'un protocole generalise sur des connexions de communications client/serveur WO1998004971A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU37270/97A AU3727097A (en) 1996-07-25 1997-07-25 Method and system for generalized protocol implementation on client/server communications connections

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US68631296A 1996-07-25 1996-07-25
US08/686,312 1996-07-25

Publications (1)

Publication Number Publication Date
WO1998004971A1 true WO1998004971A1 (fr) 1998-02-05

Family

ID=24755807

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1997/012214 WO1998004971A1 (fr) 1996-07-25 1997-07-25 Procede et systeme de mise en application d'un protocole generalise sur des connexions de communications client/serveur

Country Status (2)

Country Link
AU (1) AU3727097A (fr)
WO (1) WO1998004971A1 (fr)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999044138A2 (fr) * 1998-02-26 1999-09-02 Sun Microsystems, Inc. Exigences de securite dans des systemes a empilement
WO1999044115A2 (fr) * 1998-02-26 1999-09-02 Sun Microsystems, Inc. Designation par procede des exigences de securite
FR2785122A1 (fr) * 1998-10-27 2000-04-28 Philippe Faugeras Procede et dispositif de pilotage a distance d'un automate et carte prevue a cet effet
EP1061446A2 (fr) * 1999-06-14 2000-12-20 Sun Microsystems, Inc. Gestion d'entreprise orientée Web avec possibilité de multiples zones d'archivage
WO2001020450A2 (fr) * 1999-09-11 2001-03-22 Daimlerchrysler Ag Systeme et procede pour assister l'interaction de groupes (gia) dans des espaces d'information hypermedia
US6263350B1 (en) 1996-10-11 2001-07-17 Sun Microsystems, Inc. Method and system for leasing storage
WO2001076175A2 (fr) * 2000-03-30 2001-10-11 Telefonaktiebolaget Lm Ericsson (Publ) Cycle a duree de connexion optimisee pour relation client-serveur authentique
FR2826750A1 (fr) * 2001-06-28 2003-01-03 France Telecom Systeme de passerelle entre une plate-forme et un module logiciel externe
FR2827104A1 (fr) * 2001-07-03 2003-01-10 Elzbieta Krystyna Ploc Cochard Procede pour le controle d'echanges de donnees entre deux applications, respectivement de type client et de type serveur
WO2004042571A2 (fr) * 2002-11-06 2004-05-21 Roberto Della Pasqua Procede de communication a temps de reponse reduit dans un systeme de traitement de donnees reparti
US6862594B1 (en) 2000-05-09 2005-03-01 Sun Microsystems, Inc. Method and apparatus to discover services using flexible search criteria
EP1546865A2 (fr) * 2002-08-29 2005-06-29 BAE Systems Information and Electronic Systems Integration Inc. Systeme et procede pour remplacer des dispositifs de communication fondes sur une connexion sous-jacente dans des systemes en temps reel au moment de l'execution
US6934755B1 (en) 2000-06-02 2005-08-23 Sun Microsystems, Inc. System and method for migrating processes on a network
CN101160798B (zh) * 2005-08-22 2010-12-01 华为技术有限公司 一种实现应用业务的方法、系统及实体
US9110711B2 (en) 2000-05-09 2015-08-18 Oracle International Corporation Dynamic displays in a distributed computing environment
US9183066B2 (en) 1998-03-20 2015-11-10 Oracle America Inc. Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
CN114915651A (zh) * 2021-02-09 2022-08-16 武汉斗鱼网络科技有限公司 WebSocket的管理方法、装置、电子设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5506961A (en) * 1992-09-11 1996-04-09 International Business Machines Corporation Connection authorizer for controlling access to system resources
US5509121A (en) * 1991-09-02 1996-04-16 Hitachi, Ltd. Multi-protocol communication control apparatus

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5509121A (en) * 1991-09-02 1996-04-16 Hitachi, Ltd. Multi-protocol communication control apparatus
US5506961A (en) * 1992-09-11 1996-04-09 International Business Machines Corporation Connection authorizer for controlling access to system resources

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6263350B1 (en) 1996-10-11 2001-07-17 Sun Microsystems, Inc. Method and system for leasing storage
WO1999044115A2 (fr) * 1998-02-26 1999-09-02 Sun Microsystems, Inc. Designation par procede des exigences de securite
WO1999044115A3 (fr) * 1998-02-26 1999-11-04 Sun Microsystems Inc Designation par procede des exigences de securite
WO1999044138A3 (fr) * 1998-02-26 1999-11-04 Sun Microsystems Inc Exigences de securite dans des systemes a empilement
WO1999044138A2 (fr) * 1998-02-26 1999-09-02 Sun Microsystems, Inc. Exigences de securite dans des systemes a empilement
US6282652B1 (en) 1998-02-26 2001-08-28 Sun Microsystems, Inc. System for separately designating security requirements for methods invoked on a computer
US9183066B2 (en) 1998-03-20 2015-11-10 Oracle America Inc. Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
FR2785122A1 (fr) * 1998-10-27 2000-04-28 Philippe Faugeras Procede et dispositif de pilotage a distance d'un automate et carte prevue a cet effet
EP1061446A2 (fr) * 1999-06-14 2000-12-20 Sun Microsystems, Inc. Gestion d'entreprise orientée Web avec possibilité de multiples zones d'archivage
EP1061446A3 (fr) * 1999-06-14 2005-02-02 Sun Microsystems, Inc. Gestion d'entreprise orientée Web avec possibilité de multiples zones d'archivage
US6976262B1 (en) 1999-06-14 2005-12-13 Sun Microsystems, Inc. Web-based enterprise management with multiple repository capability
WO2001020450A2 (fr) * 1999-09-11 2001-03-22 Daimlerchrysler Ag Systeme et procede pour assister l'interaction de groupes (gia) dans des espaces d'information hypermedia
WO2001020450A3 (fr) * 1999-09-11 2001-12-06 Daimler Chrysler Ag Systeme et procede pour assister l'interaction de groupes (gia) dans des espaces d'information hypermedia
WO2001076175A2 (fr) * 2000-03-30 2001-10-11 Telefonaktiebolaget Lm Ericsson (Publ) Cycle a duree de connexion optimisee pour relation client-serveur authentique
WO2001076175A3 (fr) * 2000-03-30 2002-02-14 Ericsson Telefon Ab L M Cycle a duree de connexion optimisee pour relation client-serveur authentique
US9110711B2 (en) 2000-05-09 2015-08-18 Oracle International Corporation Dynamic displays in a distributed computing environment
US6862594B1 (en) 2000-05-09 2005-03-01 Sun Microsystems, Inc. Method and apparatus to discover services using flexible search criteria
US6934755B1 (en) 2000-06-02 2005-08-23 Sun Microsystems, Inc. System and method for migrating processes on a network
WO2003003203A1 (fr) * 2001-06-28 2003-01-09 France Telecom Systeme de passerelle entre une plate-forme et un module logiciel externe
FR2826750A1 (fr) * 2001-06-28 2003-01-03 France Telecom Systeme de passerelle entre une plate-forme et un module logiciel externe
WO2003005670A1 (fr) * 2001-07-03 2003-01-16 Elzbieta Cochard Plociennik Procede pour le controle d'echanges de donnees entre deux applications, respectivement de type client et de type serveur
FR2827104A1 (fr) * 2001-07-03 2003-01-10 Elzbieta Krystyna Ploc Cochard Procede pour le controle d'echanges de donnees entre deux applications, respectivement de type client et de type serveur
US7440959B2 (en) 2001-07-03 2008-10-21 Cochard Plociennik Elzbieta Method of controlling exchanges of data between two applications, namely a client-type application and a server-type application respectively
EP1546865A2 (fr) * 2002-08-29 2005-06-29 BAE Systems Information and Electronic Systems Integration Inc. Systeme et procede pour remplacer des dispositifs de communication fondes sur une connexion sous-jacente dans des systemes en temps reel au moment de l'execution
EP1546865A4 (fr) * 2002-08-29 2007-09-19 Bae Systems Information Systeme et procede pour remplacer des dispositifs de communication fondes sur une connexion sous-jacente dans des systemes en temps reel au moment de l'execution
WO2004042571A3 (fr) * 2002-11-06 2005-01-06 Pasqua Roberto Della Procede de communication a temps de reponse reduit dans un systeme de traitement de donnees reparti
WO2004042571A2 (fr) * 2002-11-06 2004-05-21 Roberto Della Pasqua Procede de communication a temps de reponse reduit dans un systeme de traitement de donnees reparti
CN101160798B (zh) * 2005-08-22 2010-12-01 华为技术有限公司 一种实现应用业务的方法、系统及实体
CN114915651A (zh) * 2021-02-09 2022-08-16 武汉斗鱼网络科技有限公司 WebSocket的管理方法、装置、电子设备及存储介质
CN114915651B (zh) * 2021-02-09 2023-09-26 武汉斗鱼网络科技有限公司 WebSocket的管理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
AU3727097A (en) 1998-02-20

Similar Documents

Publication Publication Date Title
KR100260682B1 (ko) 애플릿실행방법및컴퓨터워크스테이션
KR100464839B1 (ko) 서브릿을처리하기위한장치및방법
KR100331525B1 (ko) 사용자 인증 시스템 및 그 방법
US7080120B2 (en) System and method for collaborative processing of distributed applications
US6453362B1 (en) Systems, methods and computer program products for invoking server applications using tickets registered in client-side remote object registries
US6789204B2 (en) Resource sharing on the internet via the HTTP
EP1483671B1 (fr) Fourniture de services agreges dans un environnement a informatique repartie
US6323881B1 (en) Web based GUI server and method for a telecommunications node
US7194545B2 (en) Smart card applications implementing CGI agents and directory services
US5928363A (en) Method and means for preventing unauthorized resumption of suspended authenticated internet sessions using locking and trapping measures
US6170017B1 (en) Method and system coordinating actions among a group of servers
US6115744A (en) Client object API and gateway to enable OLTP via the internet
WO1998004971A1 (fr) Procede et systeme de mise en application d'un protocole generalise sur des connexions de communications client/serveur
US4885789A (en) Remote trusted path mechanism for telnet
AU776016B2 (en) System for accessing an object using a "web" browser co-operating with a smart card
US7631084B2 (en) Method and system for providing secure access to private networks with client redirection
US6438600B1 (en) Securely sharing log-in credentials among trusted browser-based applications
CA2279382C (fr) Systeme de courtage pour demandes dans le web commandant des operations multiples
US7640346B2 (en) Dispatching network connections in user-mode
AU743497B2 (en) Internet transaction processing interface
US8095599B2 (en) Mail-based web application and document delivery
US6216101B1 (en) Server and terminal emulator for persistent connection to a legacy host system with client token authentication
WO2003105403A1 (fr) Systeme de communication client-serveur
US8499031B1 (en) Markup language messaging service for secure access by edge applications
US6968356B1 (en) Method and apparatus for transferring data between a client and a host across a firewall

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE HU IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG UZ VN AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH KE LS MW SD SZ UG ZW AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 98508851

Format of ref document f/p: F

NENP Non-entry into the national phase

Ref country code: CA

122 Ep: pct application non-entry in european phase