×

Automated conversion of versioned data collections

  • US 8,898,236 B2
  • Filed: 10/31/2008
  • Issued: 11/25/2014
  • Est. Priority Date: 10/31/2008
  • Status: Active Grant
First Claim
Patent Images

1. A method of versioning an instance of a data collection, comprising:

  • receiving a request from a recipient for an instance of a data collection stored by a sender according to a sender version indicator, the instance represented during a communication session with the recipient and the data collection comprising a database record;

    identifying, from the request, a recipient version indicator representing a recipient preferred version of the data collection, the identifying comprising;

    receiving the recipient version indicator from the recipient while establishing the communication session with the recipient;

    storing the recipient version indicator; and

    retrieving the stored recipient version indicator when the request is subsequently received from the recipient;

    comparing the sender version indicator with the recipient version indicator;

    responsive to the sender version indicator preceding the recipient version indicator based upon the comparing, sending the instance to the recipient for upconverting, by the recipient, the instance to the recipient preferred version; and

    responsive to the recipient version indicator preceding the sender version indicator based upon the comparing and the sender not having stored a second instance of the data collection according to the recipient version indicator, generating, by the sender, a downconverted instance of the data collection formatted according to the recipient preferred version and sending the downconverted instance to the recipient,the generating a downconverted instance comprising;

    changing an order of serialization of members of the instance of the data collection; and

    for respective members within at least one of the instance of the data collection or the recipient preferred version of the data collection;

    responsive to a first member of the instance being formatted according to a representation format of the recipient preferred version,providing the first member for sending as at least part of the downconverted instance;

    responsive to a second member of the instance being formatted differently than the representation format of the recipient preferred version;

    translating the second member to the representation format to generate a translated member, the translating comprising at least one of;



    reordering elements associated with the second member;

    or 

    resizing blocks of memory associated with the second member if an array size of an array associated with the second member differs from a preferred version array size of the recipient preferred version to resize the array to the preferred version array size;

    serializing the translated member; and

    providing the translated member for sending as at least part of the downconverted instance;

    responsive to a third member of the recipient preferred version not being included in the instance;

    generating a default member corresponding to the third member, the default member having a default value, andproviding the default member for sending as at least part of the downconverted instance; and

    responsive to a fourth member of the instance not being included in the recipient preferred version, discarding the fourth member.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×