From 6becc3c68e2a736d57eec94159c08c5155e865d4 Mon Sep 17 00:00:00 2001 From: Christophe Dumez Date: Mon, 16 Dec 2013 09:45:55 -0500 Subject: [PATCH] The Contact constructor should not set id / lastUpdated attributes The Contact constructor should not set id / lastUpdated attributes. Those should be initially null and generate asynchronously by the call to ContactManager.save() because this is when the implementation actually interacts with the database. The specification actually already states that the save() method will set the id and lastUpdated attributes on the contact that is asynchronously returned. This issue was reported by Huang Deqing . --- index.html | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/index.html b/index.html index 5770281..4cbbe56 100644 --- a/index.html +++ b/index.html @@ -649,11 +649,7 @@

Steps

  • Let contact be a new Contact object.
  • Make a request to the system to generate a new unique contact identifier. -
  • Set the id attribute of contact to the - generated contact identifier. -
  • Set the lastUpdated attribute of contact to - the Date at which the constructor was invoked. -
  • Set the other attributes of contact to the value of the +
  • Set the attributes of contact to the value of the corresponding element in the contactInitDict dictionary, if present.