{"action":"created","issue":{"url":"https://api.github.com/repos/mbraceproject/MBrace.Azure/issues/8","labels_url":"https://api.github.com/repos/mbraceproject/MBrace.Azure/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/mbraceproject/MBrace.Azure/issues/8/comments","events_url":"https://api.github.com/repos/mbraceproject/MBrace.Azure/issues/8/events","html_url":"https://github.com/mbraceproject/MBrace.Azure/issues/8","id":58466516,"number":8,"title":"Make CloudRef and CloudArray more consistent w.r.t. IDs","user":{"login":"dsyme","id":7204669,"avatar_url":"https://avatars.githubusercontent.com/u/7204669?v=3","gravatar_id":"","url":"https://api.github.com/users/dsyme","html_url":"https://github.com/dsyme","followers_url":"https://api.github.com/users/dsyme/followers","following_url":"https://api.github.com/users/dsyme/following{/other_user}","gists_url":"https://api.github.com/users/dsyme/gists{/gist_id}","starred_url":"https://api.github.com/users/dsyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsyme/subscriptions","organizations_url":"https://api.github.com/users/dsyme/orgs","repos_url":"https://api.github.com/users/dsyme/repos","events_url":"https://api.github.com/users/dsyme/events{/privacy}","received_events_url":"https://api.github.com/users/dsyme/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-02-21T17:15:13Z","updated_at":"2015-02-23T19:58:03Z","closed_at":"2015-02-23T19:58:03Z","body":"In the Elastacloud preview edition of MBrace clusters on Azure, the APIs for CloudRef and CloudArray feel a little inconsistent w.r.t. persistence\r\n\r\n1. We have ```CloudRef.Parse(persistentId)``` but no corresponding ```CloudArray.Parse(persistentId)```\r\n\r\n2. In both cases, I feel ``Parse`` might be better named ``Existing``.\r\n\r\n3. In this formulation the way to get the persistent ID using ``(cr :> ICloudStorageEntity).Id`` is not discoverable enough.  I think it would just be better to have ID directly on the CloudRef and CloudArray types directly, since the ID is a very fundamental part of these objects.  \r\n\r\nThanks!!!!\r\nDon\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/mbraceproject/MBrace.Azure/issues/comments/75619177","html_url":"https://github.com/mbraceproject/MBrace.Azure/issues/8#issuecomment-75619177","issue_url":"https://api.github.com/repos/mbraceproject/MBrace.Azure/issues/8","id":75619177,"user":{"login":"dsyme","id":7204669,"avatar_url":"https://avatars.githubusercontent.com/u/7204669?v=3","gravatar_id":"","url":"https://api.github.com/users/dsyme","html_url":"https://github.com/dsyme","followers_url":"https://api.github.com/users/dsyme/followers","following_url":"https://api.github.com/users/dsyme/following{/other_user}","gists_url":"https://api.github.com/users/dsyme/gists{/gist_id}","starred_url":"https://api.github.com/users/dsyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsyme/subscriptions","organizations_url":"https://api.github.com/users/dsyme/orgs","repos_url":"https://api.github.com/users/dsyme/repos","events_url":"https://api.github.com/users/dsyme/events{/privacy}","received_events_url":"https://api.github.com/users/dsyme/received_events","type":"User","site_admin":false},"created_at":"2015-02-23T19:58:03Z","updated_at":"2015-02-23T19:58:03Z","body":"Fantastic! Great to know the API is progressing in these directions.\r\n\r\nI'll close this out now :)\r\n\r\nBest\r\ndon\r\n"}}