WO2009011695A1 - Système de mise en tampon de données et de notification et procédés apparentés - Google Patents

Système de mise en tampon de données et de notification et procédés apparentés Download PDF

Info

Publication number
WO2009011695A1
WO2009011695A1 PCT/US2007/073570 US2007073570W WO2009011695A1 WO 2009011695 A1 WO2009011695 A1 WO 2009011695A1 US 2007073570 W US2007073570 W US 2007073570W WO 2009011695 A1 WO2009011695 A1 WO 2009011695A1
Authority
WO
WIPO (PCT)
Prior art keywords
program
message
network
temporary buffer
host device
Prior art date
Application number
PCT/US2007/073570
Other languages
English (en)
Inventor
Harlan T. Beverly
Charles A. Musta
Original Assignee
Bigfoot Networks, Inc.
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 Bigfoot Networks, Inc. filed Critical Bigfoot Networks, Inc.
Priority to EP07812957A priority Critical patent/EP2168052A4/fr
Priority claimed from US11/778,124 external-priority patent/US8874780B2/en
Publication of WO2009011695A1 publication Critical patent/WO2009011695A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/10—Program control for peripheral devices
    • G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
    • 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/131—Protocols for games, networked simulations or virtual reality
    • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields

Definitions

  • the present disclosure relates generally to data communications, and more specifically to a system and method for managing received data at a computer device.
  • One conventional method is for the server program to periodically poll the network stack of the server operating system to determine if data has been received.
  • this method can take an undesirable amount of time, resulting in an undesirable delay in the server program responding to client requests.
  • the speed at which a client program can be notified that it has received data from the server, and the speed with which the data can be provided to the server program can also cause undesirable delay. Similar problems can occur in peer-to-peer networks, resulting in undesirable delays in communications between programs at computer devices in the peer-to-peer network.
  • FIG. 1 is a block diagram of a particular embodiment of a network arrangement incorporating teachings of the present disclosure
  • FIG. 2 is a block diagram of a particular embodiment of a computing device that incorporates teachings of the present disclosure
  • FIG. 3 is a block diagram of an alternative embodiment of a computing device and a network device that incorporates teachings of the present disclosure
  • FIG. 4 is a block diagram of an alternative embodiment of a network device and a computing device that incorporates teachings of the present disclosure.
  • FIG. 5 is a block diagram of a particular embodiment of a network device that incorporates teachings of the present disclosure.
  • a communicative interaction may be one or more of: intending to send information, sending information, requesting information, receiving information, or receiving a request for information.
  • a communicative interaction could be one directional, bi-directional, or multidirectional.
  • a communicative interaction could be relatively complex and involve two or more network elements.
  • a communicative interaction may be "a conversation" or series of related communications between a client and a server or computer devices in a peer-to-peer network - each network element sending and receiving information to and from the other.
  • a network element may be a node, a piece of hardware, software, firmware, middleware, some other component of a computing system, and/or some combination thereof.
  • a network element may have broader applicability. As such, discussions relating to gaming issues like lag, game freezes, stuttering, warping, etc. are not intended to limit the scope of the disclosure.
  • MMOG Massively Multiplayer Online Game
  • other interactive applications such as Video On Demand, entertainment distribution, information distribution, etc., may also be implemented in a manner that incorporates the teachings disclosed herein.
  • a system incorporating teachings of the present disclosure may include a processor module that monitors communications between a computer programs at different computer devices in a network, such as a client program resident on a user machine and a server program resident on a computing device remote from the user, or a program at one device in a peer-to-peer network communicating with a program at another device in the network.
  • the server program may be part of a two-tier architecture that is deployed in a hub and spoke or centralized server configuration.
  • the server program may also be utilized in a less centralized model.
  • the server program may be implemented as one of two or more client programs that perform server-like functionality.
  • a program communicating with another program in the network is referred to herein as a peer program, and the device executing the peer program as a peer.
  • an interceptor program at the peer processor module may be utilized to intercept certain externally initiated communications intended for the peer program before those communications are placed on the network stack.
  • the interceptor program can be configured to store the received communications in a buffer in application space, rather than kernel space. The interceptor program can then intercept polling requests from the peer program inquiring if data for the peer program is located at the network stack, and provide the buffered communications to the peer program in response. Because the communications are stored in application space, rather than kernel space, the data can be rapidly provided to the peer program, improving the speed with which the program can respond to the client communications.
  • a device in the network or at the peer can monitor communications from another program in the network and determine when a communication targeted for the peer program has been received. In response, the device can initiate an interrupt at the peer.
  • the interrupt handler for the interrupt accesses the interceptor program, which notifies the peer program that a communication for the peer program has been received, and provide the data to either the peer program or the interceptor program if the peer program is not yet ready for the data.
  • the interceptor program if the interceptor program is used to hold that data, it can respond with the data in user space rather than kernel space when the peer program is ready. Both methods reduce the latency in providing a received client communication to the peer program.
  • FIG. 1 a block diagram of a particular embodiment of a network arrangement that includes a host program 103 executing at a host computing device 102, a network 106 including a network device 104, and a peer program 107 executing at a computing device 108.
  • the actual location of the network device 104 may be modified in other deployments.
  • the network device may be implemented at the host computing device 102 as a network card, a processor dongle, a "Lan on Motherboard" processor, etc.
  • network 106 may be a wide area network, such as the Internet, a local area network, or some other appropriate network or bus.
  • computing devices 102 and 108 may be similar or different.
  • computing device 108 may be a local user computer, a laptop, a cellular telephone, a gaming console, a workstation, or some other appropriate device
  • host computing device 102 may be a peer computer, a workstation, a peer of computing device 108, or some other appropriate device.
  • the peer program 107 and the host program 103 may communicate with each other via the network 106, and in particular via the network device 104.
  • the peer program 107 and host program 103 may work together to provide a user of computing device 108 with an online experience.
  • peer program 107 may receive content from computer device 102 and may occasionally send requests to host program 103 in an effort to affect the content being provided or to modify data at the host program 103.
  • FIG. 1 includes only one device executing a peer program. In practice, however, host program 103 and computing device 102 may be providing content to many peers at or near the same time.
  • the peer program 107 may send communications or messages to the host program 103 to update information, request that tasks be performed, and the like.
  • the host program 103 can be an online banking application and the peer program 107 can be a web browser.
  • the peer program 107 can send requests to the host program 103 to view account information, conduct transactions, and the like.
  • the host program 103 can determine if the requested tasks are authorized and, if so, execute the tasks.
  • the host program 103 is a server game program and the peer program 107 is a peer-side game program that provides a user with an online- gaming experience.
  • the host program 103 and the peer program 107 work together to provide a game simulation experience to two or more players at each computer device 102 and 106.
  • the peer program 107 sends messages via the network 106, and in particular to the network device 104.
  • Each message includes information, such as address information, indicating the location of the computer device 102.
  • Each message also includes port information, indicating the target port of the computer device 102 with which the message is associated.
  • the network device 104 delivers messages from network to the computer device 102.
  • the computer device 102 also includes an interceptor program 105 that monitors message from the network device 104. If a message is not targeted to the host program 103, the interceptor program 105 provides the message to a network stack at the computer device 102 or to some other program to which the data is targeted.
  • the network stack can subsequently be accessed by other programs (not shown) executing at the computer device 102 to retrieve the message, or the data is delivered to a different program (not shown).
  • the interceptor program 105 intercepts the message and stores it in a buffer for the host program 103.
  • the buffer is "logically close" to the host program 103 so that it can be quickly accessed. Accordingly, when the host program 103 inquires (such as through a polling request) whether a message has been sent from a peer program 107, the interceptor program 105 receives the inquiry and provides a response more rapidly than the message could be retrieved from the network stack.
  • the interceptor program 105 improves the communication efficiency between the peer program 107 and the host program 103. This reduces the likelihood of latency problems and provides for an improved user experience. Further, because the interceptor program 105 is located "between" the peer program 107 and the host program 103, it can be implemented without redesign of the host program 103 or the peer program 107. Accordingly, deployment of the interceptor program 105 is simplified.
  • the host program 103 is designed to frequently poll the network stack to check if a peer program 107 has been transmitted data intended for the host program 103. These polling requests can cause additional processing power to be consumed slowing overall operation. Because the interceptor program 105 can hold buffers and data ready information logically close to the host program 103 and provide the polling answer more quickly, processing power at the computer device 102 is conserved.
  • some or all of the interceptor program 105 could reside in the network device 104.
  • the interceptor program 105 could use buffers which reside in the network device 104 to conserve the amount of buffer space needed in the computer device 102.
  • the portion of the interceptor program 105 described above which has knowledge of if there is data available or not could still reside in user space, therefore giving similar improvements in polling.
  • Buffered data could reside in the network device 104, and be transferred directly to the host program 103 when the data was requested by the host program 103. This method conserves memory usage in the computer device 102 and also conserves processing power when the host program 103 is polling for information if data is available or not.
  • the network device 104 provides an interrupt to the computer device 102 when a message targeted to the host program 103 is received.
  • the computer device 102 executes the interceptor program 105, which receives the message from the network device 104.
  • the host program 103 may have outstanding receive commands and so would be immediately and notified that the message has been received.
  • the host program may poll or post a receive at some later time, at which point the data would be delivered as described above.
  • the host program 103 retrieves the message from the interceptor program 105.
  • the computer device 202 includes application space 220 and kernel space 230.
  • kernel space refers to memory address space that is typically only accessible by the kernel of an operating system at the computer device 202.
  • Applications executing at the computer device 202 typically cannot access the kernel space directly, but instead must request information stored in the kernel space from the operating system kernel.
  • Application space refers to memory address space that is accessible by applications at the computer device 202.
  • Applications can typically access information stored in the application space 220 more quickly than information stored in the kernel space 230, because accesses to the application space 220 are not typically performed through the kernel.
  • both the kernel space 230 and the application space 220 can be virtual memory address spaces.
  • the application space 220 includes a host program 203, a program 207, and a temporary buffer 225.
  • the kernel space 235 includes a network stack 235.
  • the computer device 202 also includes an interceptor program 205 that, as illustrated, resides in both kernel space 235 and application space 220.
  • the network stack 235 is configured to store messages and other information received from the network 106.
  • the network stack 235 is accessed by the kernel in response to requests from applications executing at the computer device 202.
  • the kernel can determine if the network stack stores data for the requesting application and, if so, provide the data. Because the kernel typically executes a number of tasks in addition to accessing the network stack 235, accessing the network stack typically takes more time than an access to data stored in the application space 220.
  • the interceptor program 205 monitors messages received from the network 106. If a message is not targeted to the host program 203, the interceptor program 205 provides the message to the network stack 235 or to the program it is directed to, so that it is available for access by other programs at the computer device 202, such as the program 207. If the received message is targeted to the host program 203, the interceptor program stores the message in the temporary buffer 225 or an indication that the data is ready in the temporary buffer 225. In an alternative implementation a temporary data buffer is stored in kernel space 230 and only the indication that data is ready is stored in the temporary buffer 225. In yet another implementation, the indication that data is ready is stored in the temporary buffer 225, but the data itself is given to the network stack 235.
  • the interceptor program 205 also monitors communications between the host program 203 and the kernel to determine if the host program 203 is attempting to access the network stack 235. For example, the host program 203 may periodically poll the network stack 235 to determine if a message targeted to the program has been received from the network 106.
  • the polling request to check the network stack 235 can be a poll request, a blocking select request, a non- blocking select request, a blocking receive request, a non-blocking receive request, or an asynchronous receive request, or any other such request as is used to determine if data is available.
  • the interceptor program 205 detects a polling request from the host program 203, it intercepts the request and determines if a message for the host program 203 is stored in the temporary buffer 225 or if the temporary buffer 225 indicates that data is ready to receive. If no message is stored in the temporary buffer 225 or there is no indication that data is ready to be received, the interceptor program 205 notifies the host program 203. If a message is stored in the temporary buffer 225, the interceptor program 205 either notifies the host program or when asked, provides the data to the host program 203.
  • the interceptor program 205 is able to indicate whether or not there is data ready for the host program more quickly than it would be able to from the network stack 235.
  • the interceptor program 205 is able to provide the stored message more quickly than it would be provided by the kernel from the network stack 235.
  • FIG. 3 a block diagram of a particular embodiment of a computer device 302 and a network device 304 are illustrated, corresponding to the computer device 102 and the network device 104, respectively, of FIG. 1.
  • the network device 304 includes an interceptor program 350.
  • the computer device 302 includes application space 320, kernel space 330, an interceptor program 305, and an interrupt handler 340.
  • the application space 320 includes a host program 303 and a temporary buffer 325.
  • the kernel space 330 includes a network stack 335.
  • the network device 304 receives messages from the peer program 107 via the network 106.
  • the interceptor program 350 monitors messages received from the network 106 and determines which of those messages are targeted to the host program 303.
  • the interceptor program 350 provides messages not targeted to the host program 303 to the network stack 335 of the computer device 302 or to a different program (not shown).
  • the network device 304 can send an interrupt indicator to the computer device 302.
  • the computer device 302 invokes the interrupt handler 340, which stores an indication that the message has been received in the temporary buffer 325.
  • the message itself can be stored in the temporary buffer 325, in another buffer (not shown) in application space 320, in kernel space 330, or in the network stack 335.
  • the temporary buffer can be located at the network device 304.
  • the interceptor program 305 accesses the temporary buffer 325 to determine that a message associated with the host program 303has been received and notifies the host program 303 that the message is available. Further, the interceptor program can retrieve the message and provide it to the host program 303. Because the indication that the message has been received is not placed on the network stack 335, notification of the received message can be provided more quickly to the host program 303, thereby improving communication efficiency between the peer program 107 and the host program 103. In an alternative embodiment, the interceptor program 305 intercepts polling requests from the host program 303 that are targeted to the network stack.
  • the interceptor program 305 determines, based on the contents of the temporary buffer 325, whether a message targeted to the host program 303 has been received. If no message has been received, the interceptor program 305 responds to the polling request to indicate no message is available. If a message has been received, the interceptor program 305 retrieves the message (from the temporary buffer 325, from another buffer in application space, from a buffer in kernel space 330, or from the network stack 335) and provides the message to the host program 303. Because the interceptor program 305 does not access the kernel space 330 in order to determine whether a message is available, it can respond to poll requests from the host program 303 more quickly than if the requests were to proceed directly to the network stack 335.
  • the network device 404 includes an interceptor program 450.
  • the computer device 402 includes application space 420 and kernel space 430.
  • the application space 420 includes a host program 403, an interceptor program 405, and a temporary buffer 425.
  • the kernel space 430 includes a network stack 435.
  • the interceptor program 450 is configured to access the temporary buffer 425 and the network stack 435.
  • the interceptor program 405 is configured to interface with the host program 403, the network stack 435, and the temporary buffer 425.
  • the network device 404 receives messages from the peer program 107 via the network 106.
  • the interceptor program 450 monitors messages received from the network 106 and determines which of those messages are targeted to the host program 403.
  • the interceptor program 450 provides messages not targeted to the host program 403 to the network stack 435 of the computer device 402 or to a different program (not shown). If a message is targeted to the host program 403, the interceptor program 405 can store the message or an indication that there is a new message available in the temporary buffer 425.
  • the interceptor program 405 monitors communications between the host program 403 and the kernel to determine if the host program 403 is attempting to access the network stack 435. For example, the host program 403 may periodically poll the network stack 435 to determine if a message targeted to the program has been received from the network 106. If the interceptor program 405 detects a polling request from the host program 403, it intercepts the request and determines if a message for the host program 403 is stored in the temporary buffer 425 or if the temporary buffer indicates that data is ready to receive. If no message is stored there or there is no indication that data is ready to be received, the interceptor program 405 notifies the host program 403.
  • the interceptor program 405 determines whether a message is available for the host program 403 without accessing the network stack, it can respond to polling requests quickly, thereby improving the performance of the host program 403
  • FIG. 5 a block diagram of a particular embodiment of a network device 504, corresponding to the network device 504, is illustrated.
  • the network device 504 includes a processor 570 and a memory 560.
  • the memory 560 is accessible to the processor 570.
  • the processor 570 can be a microprocessor, microcontroller, and the like.
  • the memory 560 is a computer readable medium that can be volatile memory, such as random access memory (RAM), or non-volatile memory, such as a hard disk or flash memory.
  • the memory 560 stores an interceptor program 550 and an operating system 507.
  • the interceptor program 550 and the operating system 507 include instructions to manipulate the processor 570 in order to implement one or more of the methods described herein.
  • Other programs, such as applications, can also be stored in the memory 560 to manipulate the processor in order to implement the described methods.
  • the computer device 102 could be configured similarly to the network device 504, including a memory to store one or more programs to manipulate a processor to implement one or more of the methods described herein.

Abstract

Un programme intercepteur dans un dispositif informatique intercepte certaines communications initiées de manière externe destinées pour un programme homologue avant que ces communications ne soient placées sur la pile réseau. En outre, le programme intercepteur stocke les communications reçues dans un tampon dans un espace d'application, plutôt que dans un espace de noyau. Le programme intercepteur peut ensuite intercepter des requêtes d'invitation à émettre provenant du programme homologue demandant si des données pour le programme homologue sont situées dans la pile réseau, et fournir les communications mises en tampon au programme homologue en réponse. En raison du fait que les communications sont stockées dans l'espace d'application, plutôt que dans l'espace de noyau, les données peuvent être fournies rapidement au programme homologue, améliorant la vitesse à laquelle le programme peut répondre aux communications clients.
PCT/US2007/073570 2006-07-17 2007-07-16 Système de mise en tampon de données et de notification et procédés apparentés WO2009011695A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07812957A EP2168052A4 (fr) 2007-07-16 2007-07-16 Système de mise en tampon de données et de notification et procédés apparentés

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US60/807,530 2006-07-17
US11/778,124 US8874780B2 (en) 2006-07-17 2007-07-16 Data buffering and notification system and methods thereof

Publications (1)

Publication Number Publication Date
WO2009011695A1 true WO2009011695A1 (fr) 2009-01-22

Family

ID=40259888

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/073570 WO2009011695A1 (fr) 2006-07-17 2007-07-16 Système de mise en tampon de données et de notification et procédés apparentés

Country Status (2)

Country Link
EP (1) EP2168052A4 (fr)
WO (1) WO2009011695A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060075119A1 (en) * 2004-09-10 2006-04-06 Hussain Muhammad R TCP host
US20060253605A1 (en) * 2004-12-30 2006-11-09 Prabakar Sundarrajan Systems and methods for providing integrated client-side acceleration techniques to access remote applications
US20060251109A1 (en) * 2005-04-05 2006-11-09 Shimon Muller Network system
US20060294234A1 (en) * 2005-06-22 2006-12-28 Cisco Technology, Inc. Zero-copy network and file offload for web and application servers
US20070094643A1 (en) * 2005-10-25 2007-04-26 Anderson Eric A System and method for writing captured data from kernel-level to a file
US20070162639A1 (en) 2005-11-30 2007-07-12 Chu Hsiao-Keng J TCP-offload-engine based zero-copy sockets

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6675218B1 (en) * 1998-08-14 2004-01-06 3Com Corporation System for user-space network packet modification
WO2004001615A1 (fr) * 2002-06-19 2003-12-31 Telefonaktiebolaget Lm Ericsson Architecture de logiciel pilote de reseau

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060075119A1 (en) * 2004-09-10 2006-04-06 Hussain Muhammad R TCP host
US20060253605A1 (en) * 2004-12-30 2006-11-09 Prabakar Sundarrajan Systems and methods for providing integrated client-side acceleration techniques to access remote applications
US20060251109A1 (en) * 2005-04-05 2006-11-09 Shimon Muller Network system
US20060294234A1 (en) * 2005-06-22 2006-12-28 Cisco Technology, Inc. Zero-copy network and file offload for web and application servers
US20070094643A1 (en) * 2005-10-25 2007-04-26 Anderson Eric A System and method for writing captured data from kernel-level to a file
US20070162639A1 (en) 2005-11-30 2007-07-12 Chu Hsiao-Keng J TCP-offload-engine based zero-copy sockets

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2168052A4

Also Published As

Publication number Publication date
EP2168052A4 (fr) 2011-03-09
EP2168052A1 (fr) 2010-03-31

Similar Documents

Publication Publication Date Title
US8874780B2 (en) Data buffering and notification system and methods thereof
US20200195537A1 (en) Load balancing web service by rejecting connections
Daglis et al. RPCValet: NI-driven tail-aware balancing of µs-scale RPCs
Jose et al. Memcached design on high performance RDMA capable interconnects
US8543692B2 (en) Network system
US20080240144A1 (en) File server pipelining with denial of service mitigation
CN102402462A (zh) 用于对启用gpu的虚拟机进行负载平衡的技术
US20070060373A1 (en) Data communication system and methods
US8205214B2 (en) Browser elements for communicating with other browser elements and with external applications
CN102323888B (zh) 一种无盘计算机启动加速方法
US20100113158A1 (en) Method and apparatus for hosting a distributed virtual world system
US10592374B2 (en) Remote service failure monitoring and protection using throttling
WO2007040581A2 (fr) Systeme et procede pour effectuer des operations 'pause' et 'reprise' sur des destinations
EP2115619B1 (fr) Dispositif de controle d'etat d'interface de connexion de communication et procedes associes
WO2010030695A2 (fr) Messagerie mise en file d’attente asynchrone destinée à des applications web
WO2009011695A1 (fr) Système de mise en tampon de données et de notification et procédés apparentés
CN112764837B (zh) 数据上报方法、装置、存储介质及终端
KR20080059934A (ko) 논 블록킹 입출력을 이용한 서버의 쓰레드 관리 방법 및시스템
KR20090064366A (ko) 데이터 버퍼링 및 통지 시스템 및 그 방법들
JP6786835B2 (ja) 管理装置、サーバ、シンクライアントシステム、管理方法及びプログラム
Wang et al. A scalable queuing service based on an in-memory data grid
CN114296916B (zh) 一种提高释放rdma性能的方法、装置及介质
JP4695614B2 (ja) アクセス管理装置、アクセス管理方法、アクセス管理プログラム
US10819799B2 (en) Method for dynamic retention of HTTP session information and web application server and web server using the same
Ostrowick Network Booting versus hard disks: Costs and Implications

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2007812957

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020097003187

Country of ref document: KR

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07812957

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE