# US 10,484,449 B2 · Email webclient notification queuing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,484,449 B2 - Document ID: US10484449B2 - Status: Granted - Kind: B2 - Application number: 15/898,137 - Filed: 2018-02-15 - Published: 2018-08-23 - Granted: 2019-11-19 - Earliest claimed: 2013-09-17 - Assignees: Amazon Technologies, Inc. - Applicants: Amazon Technologies, Inc. - Inventors: Daniel Christianto; Ivo van Doorn; Simon Arthur Koster - Web page: https://patentgrep.com/patent/US10484449B2 ## CPC - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L 51/08: Annexed information, e.g. attachments - H04L 51/224: providing notification on incoming messages, e.g. pushed notifications of received messages - H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Notifications received from an email server can be stored and provided to a webclient upon subsequent communications from the webclient received at an HTTP server. Notifications stored in a database or a storage are retrieved and transmitted to the webclient by backup or alternate HTTP servers when the webclient requests service. An attachment received from a webclient for a message in composition can be saved by an HTTP server in a storage system so that a backup HTTP server can locate the attachment and provide the attachment to a messaging server when the user is ready to send the message. ## Claims ### Claim 1 An email notification method comprising: establishing a persistent connection to an email server in response to receiving a message that a first HTTP server is servicing a webclient; receiving a first notification from the email server indicative that email has been received for the webclient; storing the first notification in a storage location; and in response to receiving a communication from the first HTTP server, providing information to the first HTTP server to retrieve the stored first notification from the storage location; and in response to receiving a subsequent communication from a second HTTP server, providing information to the second HTTP server to retrieve one or more notifications stored in the storage location subsequent to the first notification. ### Claim 2 (depends on 1) The method as recited in claim 1, wherein the first notification is stored in a database in the storage location, the first notification stored based on information identifying the webclient. ### Claim 3 (depends on 2) The method as recited in claim 2, further comprising causing the first notification to be deleted from the database based upon a predetermined event. ### Claim 4 (depends on 3) The method as recited in claim 3, wherein the predetermined event comprises a preset time. ### Claim 5 (depends on 1) The method as recited in claim 1 further comprising transmitting an acknowledgement of receipt of the notification to the to the email server. ### Claim 6 (depends on 1) The method as recited in claim 1 further comprising associating a session identifier with the stored notification. ### Claim 7 (depends on 1) The method as recited in claim 1 wherein the communication comprises a subscription to notifications associated with the webclient. ### Claim 8 An email notification system, comprising: one or more computing processors having stored thereon computer readable instructions that upon execution by the one or more computing processors, at least cause the system to: establish a persistent connection to an email server in response to receiving a message that a first HTTP server is servicing a webclient; receive information from the email server indicative that at least one email message has been received for the webclient; store information indicative of a first notification that at least one email message has been received based on the received information; and in response to receiving a communication from the first HTTP server, provide information to the first HTTP server to retrieve the stored first notification; and in response to receiving a subsequent communication from a second HTTP server, provide information to the second HTTP server to retrieve one or more notifications stored subsequent to the first notification. ### Claim 9 (depends on 8) The system as recited in claim 8, wherein the first notification is stored in a database in the storage location, the first notification stored based on information identifying the webclient. ### Claim 10 (depends on 8) The system as recited in claim 8, wherein the computer readable instructions that upon execution by the one or more computing nodes, at least cause the system to cause the notification to be deleted based upon a predetermined event. ### Claim 11 (depends on 10) The system as recited in claim 10, wherein the predetermined event comprises a preset time. ### Claim 12 (depends on 8) The system as recited in claim 8 wherein the computer readable instructions that upon execution by the one or more computing nodes, at least cause the system to transmit an acknowledgement of receipt of the notification to the to the email server. ### Claim 13 (depends on 8) The system as recited in claim 8 wherein the computer readable instructions that upon execution by the one or more computing nodes, at least cause the system to associate a session identifier with the stored notification. ### Claim 14 (depends on 8) The system as recited in claim 8 wherein the communication comprises a subscription to notifications associated with the webclient. ### Claim 15 A message notification system, comprising: one or more computing processors that upon execution of computer readable instructions configure the system at least to: establish a persistent connection to a message server in response to receiving a message that a first HTTP server is servicing a webclient; receive information from the message server indicative that at least one message has been received addressed to an account associated with the webclient; store information indicative of a first notification that at least one message has been received based on the received information; and in response to receiving a communication from the first HTTP server, provide information to the first HTTP server to retrieve the stored first notification; and in response to receiving a subsequent communication from a second HTTP server, provide information to the second HTTP server to retrieve one or more notifications stored subsequent to the first notification. ### Claim 16 (depends on 15) The system as recited in claim 15, wherein the first notification is stored in a database in the storage location, the first notification stored based on information identifying the webclient. ### Claim 17 (depends on 16) The system as recited in claim 16, wherein the computer readable instructions upon execution further configure the system to cause the notification to be deleted based upon a predetermined event. ### Claim 18 (depends on 17) The system as recited in claim 17, wherein the predetermined event comprises a preset time. ### Claim 19 (depends on 15) The system as recited in claim 15 wherein the computer readable instructions upon execution further configure the system to transmit an acknowledgement of receipt of the notification to the to the message server. ### Claim 20 (depends on 15) The system as recited in claim 15 wherein the computer readable instructions upon execution further configure the system to associate a session identifier with the stored notification.