Apparatus and method for maintaining a message thread with opt-in permanence for entries

  • US 9,742,713 B2
  • Filed: 05/09/2014
  • Issued: 08/22/2017
  • Est. Priority Date: 05/30/2013
  • Status: Active Grant
  • ×
    • Pin
First Claim
Patent Images

1. A server, comprising:

  • a processor; and

    a memory storing a message thread module with instructions executed by the processor to maintain a message thread between users of client devices byserving a message thread with a new text entry to a client device in response to a request for the message thread from a user;

    collecting message thread state change from the client device, wherein the message thread state change represents an indication to automatically delete the new text entry of the message thread after the duration of a transitory display period on the client device unless an indication of a gesture applied to a display screen presenting the new text entry of the message thread is received from the client device during the transitory display period, wherein the transitory display period is a single digit number of seconds, and absence of the indication of the gesture causes the indication to automatically delete the new text entry such that the new text entry is only viewed once for the single digit number of seconds;

    queuing the message thread state change at the server along with additional message thread state changes associated with the collecting operation performed for additional users and corresponding additional client devices associated with the message thread;

    revising the message thread based upon the message thread state change and the additional message thread state changes to form shared message thread state, wherein revising includes asynchronous batch mode processing in response to a satisfied synchronization condition;

    storing persistently the shared message thread state until a next synchronization event; and

    supplying the shared message thread state in response to a request for the message thread from a user that occurs after the next synchronization event and supplying the message thread with the new text entry in response to a request for the message thread from a user that occurs before the next synchronization event.

View all claims
    ×
    ×

    Thank you for your feedback

    ×
    ×