SYSTEM AND METHOD FOR IMPROVED SYNCHRONIZATION BETWEEN A SERVER AND A CLIENT

• US 20130297709A1
• Filed: 04/12/2013
• Published: 11/07/2013
• Est. Priority Date: 01/03/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Warren, Joseph R., Froelich, Karl, Lemarchand, Remi A., Novitskey, Robert R., Gray, Ronald E., Hartwell, Aaron, Power, Brendan, Curtis, Brent, Bonilla, Nicole A.
• Granted Patent: US 9,590,927 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/234 for tracking messages
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing

Abstract

A system and method for improved client and server communications, more particularly, an improved protocol that may be used for communication between a client and a server, such as in an email environment. Many features are provided for improved communications. An email server may provide the best message body available for an email message, may transfer an entire data object if requested property or properties are not well defined within the data object, may provide progress data for use in tracking download progress, and may send error information for a data object having an error. Email changes may be optimized at an email server component, even if the email changes occurred at another email server component. An email server may maintain a table of changes that occur to folders at an associated data store, and may notify a subscribed email client component of changes that occur in the table.

Claims

1-21. -21. (canceled)

22. A system comprising:

an email server component of an email server computing system, the email server component configured to receive a request from an email client component for delivery of at least one message having a body to the email client component, the request including an identifier of a body format preference, the body format preference identifying a body format from among a plurality of available body formats;

wherein, for each of the one or more messages, the email server component selects a body formatted according to the identifier.

23. The system of claim 22, wherein the body of the at least one message is formatted according to a markup language format.

24. The system of claim 23, wherein the markup language format comprises an HTML format.

25. The system of claim 22, wherein selection of the body by the email server component is limited to a body format selected from among the plurality of available body formats.

26. The system of claim 25, wherein the email client component is configured to convert the body to a second format different from the body formatted according to the identifier.

27. The system of claim 22, wherein the identifier is included in the request as a BEST_BODY flag.

28. The system of claim 22, wherein the at least one message further includes a header.

29. The system of claim 28, wherein the email server component is configured to transmit the header prior to transmitting the body of the at least one message to the email client component.

30. The system of claim 22, wherein the email server component is configured to transmit the at least one message to the email client component, wherein the at least one message includes a header and the formatted body, the formatted body based on the identifier.

31. A system comprising:

an email client component of an email client computing system, the email client component configured to transmit to an email server component a request for delivery of at least one message having a body from the email server component, the request including an identifier of a body format preference, the body format preference identifying a body format from among a plurality of available body formats;

wherein, for each of the one or more messages, the email client component receives, in response to the request, a body formatted according to the identifier.

32. The system of claim 31, wherein the at least one message is transmitted by the email server component to the email client component.

33. The system of claim 32, wherein the email server component operates on an email server computing system remote from the email client computing system.

34. The system of claim 31, wherein the body of the at least one message is formatted according to a markup language format.

35. The system of claim 34, wherein the markup language format comprises an HTML format.

36. The system of claim 31, wherein the body of the at least one message is formatted according to a body format selected from a group of email message body formats comprising:

a Rich text format (RTF);

a Hypertext Transfer Protocol (HTTP) format; and

a plain text format.

37. The system of claim 31, wherein the identifier is included in the request as a BEST_BODY flag.

38. The system of claim 31, wherein the body has a non-standard body format.

39. The system of claim 38, wherein the email client component is configured to convert the body to a second format different from the body format selected based on the identifier.

40. A computer-readable medium comprising computer-executable instructions stored thereon, which, when executed on a computing system, cause the computing system to perform a method comprising:

generating a request for delivery of at least one message having a body, the request including an identifier of a body format preference, the body format preference identifying a body format from among a plurality of available body formats;

transmitting the request to an email server component;

in response to the request, receiving the at least one message, wherein the at least one message includes a body formatted according to the identifier.

41. The computer-readable medium of claim 40, wherein the at least one messages is transmitted by the email server component to the email client component.