IP Library Granted Patent US 9,037,735
Granted Patent B1
US 9,037,735 · App. 13/837,301 · Granted May 19, 2015

Establishing websocket protocol extensions

Inventors: John R. Fallows (Palo Alto, CA); Steven R. Atkinson (Morgan Hill, CA)
Assignee: Kaazing Corporation
H04L67/42H04L69/24H04L65/1069H04L5/1438H04L65/1083H04L67/141G06F17/30861
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,037,735
App. No.
13/837,301
Granted
May 19, 2015
Kind
B1
Abstract

A request to upgrade a connection to a WebSocket connection is received. A response that the connection has been upgraded to the WebSocket connection is provided. The WebSocket connection utilizes a WebSocket protocol. An identification of a set of one or more extensions to the WebSocket protocol of the WebSocket connection is received via the WebSocket connection.

Claims (30)

1. A system, comprising:

a communication interface configured to:

receive a request to upgrade a connection to a WebSocket connection;

provide a response that the connection has been upgraded to the WebSocket connection, wherein the WebSocket connection utilizes a WebSocket protocol; and

receive via the WebSocket connection, after the response has been received, an identification of a set of one or more extensions to the WebSocket protocol of the WebSocket connection; and a processor coupled with the communication interface.

2. The system of claim 1 , wherein the WebSocket connection is a bi-directional and full-duplex communication channel.

3. The system of claim 1 , wherein the connection requested to be upgraded to the WebSocket connection includes an HTTP connection.

4. The system of claim 1 , wherein the request identifies one or more subprotocols supported by a sender of the request.

5. The system of claim 1 , wherein the request identifies a second set of one or more extensions to the WebSocket protocol.

6. The system of claim 1 , wherein the request identifies a second set of one or more extensions to the WebSocket protocol natively supported by a web browser application.

7. The system of claim 6 , wherein the set of one or more extensions identified by the identifier received via the WebSocket connection is not natively supported by the web browser.

8. The system of claim 1 , wherein the communication interface is further configured to provide a component configured to handle the WebSocket connection.

9. The system of claim 8 , wherein the component includes a software library component at least in part implementing a WebSocket API.

10. The system of claim 8 , wherein providing the component includes inserting program code.

11. The system of claim 8 , wherein the component is preconfigured to request the set of one or more extensions.

12. The system of claim 1 , wherein the communication interface is further configured to provide a second response identifying support for one or more of the extensions in the set of one or more extensions.

13. The system of claim 1 , wherein the communication interface is further configured to provide a second response in response to the received identification and the second response includes an HTTP communication status identifier.

14. The system of claim 1 , wherein the response identifies a first selected subprotocol of the WebSocket connection.

15. The system of claim 14 , wherein the received identification is encoded in the first selected subprotocol.

16. The system of claim 14 , wherein the communication interface is further configured to provide a second response identifying support for one or more of the extensions in the set of one or more extensions and the second response identifies a second selected subprotocol.

17. The system of claim 1 , wherein the received identification is encoded in the WebSocket protocol.

18. The system of claim 1 , wherein the set of one or more extensions is dynamically determined.

19. A method, comprising:

receiving via a communication interface a request to upgrade a connection to a WebSocket connection;

providing a response that the connection has been upgraded to the WebSocket connection, wherein the WebSocket connection utilizes a WebSocket protocol; and

receiving via the WebSocket connection, after the response has been received, an identification of a set of one or more extensions to the WebSocket protocol of the WebSocket connection.

20. A computer program product, the computer program product being embodied in a non-transitory tangible computer readable storage medium and comprising computer instructions for:

receiving a request to upgrade a connection to a WebSocket connection;

providing a response that the connection has been upgraded to the WebSocket connection, wherein the WebSocket connection utilizes a WebSocket protocol; and

receiving via the WebSocket connection, after the response has been received, an identification of a set of one or more extensions to the WebSocket protocol of the WebSocket connection.

Assignments (4)
SECURITY INTEREST Recorded Mar 7, 2017
From: KAAZING CORPORATION
To: COMERICA BANK
Reel/Frame 041485/0708 →
SECURITY INTEREST Recorded Jun 15, 2016
From: KAAZING CORPORATION
To: US VC PARTNERS, L.P.
Reel/Frame 038915/0452 →
SECURITY INTEREST Recorded Jun 3, 2016
From: KAAZING CORPORATION
To: SQN VENTURE INCOME FUND, LP
Reel/Frame 038799/0524 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2013
From: FALLOWS, JOHN R.; ATKINSON, STEVEN R.
To: KAAZING CORPORATION
Reel/Frame 030722/0489 →