Eureka-AI is an intelligent assistant for R&D personnel, combined with Patent DNA, to facilitate innovative research.
Eureka AI

8604 results about "Server-side" patented technology

Server-side refers to operations that are performed by the server in a client–server relationship in a computer network.

Methods and apparatus for restricting access of a user using random partial biometrics

A biometrics security method and apparatus are disclosed that restrict the ability of a user to access a device or facility using a portion of biometric data to validate the user's identity. Upon a user request to access a secure device or facility, the central biometric security system initially sends a first request for a specific sample of a portion of the user's biometric information. The specific sample may be identified, for example, using a set of image coordinates. A second request is also sent to retrieve the biometric prototype from a database of registered users. The central biometric security system then compares the user biometrics portion with the corresponding biometrics prototype portions. The user receives access to the requested device if the user biometrics portion(s) matches the corresponding biometrics prototype portions. In one variation, the biometric security system transmits a security agent to the user's computing device upon a user request to access a remote device. The security agent serves to extract user biometric portions in accordance with the sampling request from the central biometric security system. In another variation, a local recognition is performed before a remote recognition to reduce the risk of a failed server side recognition due to a poor biometrics feature.

Cooperative proxy auto-discovery and connection interception

In a network supporting transactions between clients and servers and proxies that are interposable in a network path between at least one client and at least one server, wherein a pair of proxies can modify a packet stream between a client and a server such that packet data from the client to the server is transformed at a client-side proxy of the proxy pair and untransformed at a server-side proxy of proxy pair and such that packet data from the server to the client is transformed at the server-side proxy and untransformed at the client-side proxy, a method and apparatus for a discovering proxy to transparently discover its position in a proxy pair by using proxy signals to indicate to other proxies that could pair with the discovering proxy. A discovering proxy might determine that it is a client-side proxy by receipt of a packet from client without a proxy signal. A discovering proxy might determine that it is a server-side proxy by receipt of a packet from server without a return proxy signal. Once a proxy pair is discovered, that proxy pair might transform traffic from the server to the client or vice versa, transforming the traffic at one proxy of the proxy pair and untransforming the traffic at the other proxy of the pair.

System and method for achieving highly scalable real-time collaboration applications using HTTP

InactiveUS20080147834A1Highly scalable and highly responsiveDigital computer detailsTransmissionApplication serverApplication software
A highly scalable and highly responsive RTC system uses asynchronous or non-blocking I/O and HTTP response queuing to avoid server overload. The system distinguishes between two types of requests: an update request and a change request. An update request is a request used to fetch an update or change notification. A change request is a request to change some data related to the real-time session. For a given RTC session, the server first checks whether any updates exist for an update request. If an update exists, the server code can send an immediate response to the client. However, if no update exists, the server code application sets a well-defined HTTP response header, and then responds. Once the server code application responds, all application server resources are freed, and the application server is free to handle the next requests without blocking any thread. The existence of the well-defined response header, allows the lower level networking code to queue the response, allowing it to be later addressed by the RTC session ID. This way, the HTTP response can be delayed (queued) without blocking a thread in the application server. A Change Request is a request used to change some data related to the real-time session. Such requests would typically be tied to an action within a given RTC session (e.g., adding text to a chat, changing a slide, etc.). When these actions are sent to the server, the server-side application can determine whether the request affects the queued responses that are awaiting change notifications. In the case of a change, the notification response is computed, and then an API call into the lower-level network flushes all queued responses awaiting updates in the session. Therefore this mechanism is used to trigger the responses to complete, thus providing immediate updates to clients.

Posting/subscribing system for adding message queue models and working method thereof

The invention provides a posting/subscribing system for adding message queue models and a working method of the posting/subscribing system. The system comprises a distributed message-oriented middleware server-side cluster, a client-side cluster and a distributed coordinate server cluster. Service nodes in the message-oriented middleware server-side cluster are composed of corresponding modules of an original posting/subscribing system, and the function of the message-oriented middleware server-side cluster is the same as the information transferring relation; a client side is simultaneously provided with a calling interface of a posting/subscribing model and a calling interface of a message queue model which are used for achieving the purpose that a user can select and use the two different message transferring models directly without transforming the bottom layer middleware, so that a coordinate service module and a message processing module are additionally arranged on the client side based on an original framework. The system supports the posting/subscribing message transferring model and the message queue message transferring model simultaneously and guarantees that the availability, flexibility and other performance of the two models are all within the acceptable range, and the problem that it is difficult to transform the bottom layer message transferring model for the user is better solved.
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Try Eureka
PatSnap group products