{"action":"created","issue":{"url":"https://api.github.com/repos/pharo-nosql/voyage/issues/52","repository_url":"https://api.github.com/repos/pharo-nosql/voyage","labels_url":"https://api.github.com/repos/pharo-nosql/voyage/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/pharo-nosql/voyage/issues/52/comments","events_url":"https://api.github.com/repos/pharo-nosql/voyage/issues/52/events","html_url":"https://github.com/pharo-nosql/voyage/issues/52","id":169138888,"number":52,"title":"session-based object cache?","user":{"login":"dalehenrich","id":623951,"avatar_url":"https://avatars.githubusercontent.com/u/623951?v=3","gravatar_id":"","url":"https://api.github.com/users/dalehenrich","html_url":"https://github.com/dalehenrich","followers_url":"https://api.github.com/users/dalehenrich/followers","following_url":"https://api.github.com/users/dalehenrich/following{/other_user}","gists_url":"https://api.github.com/users/dalehenrich/gists{/gist_id}","starred_url":"https://api.github.com/users/dalehenrich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dalehenrich/subscriptions","organizations_url":"https://api.github.com/users/dalehenrich/orgs","repos_url":"https://api.github.com/users/dalehenrich/repos","events_url":"https://api.github.com/users/dalehenrich/events{/privacy}","received_events_url":"https://api.github.com/users/dalehenrich/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-03T14:01:54Z","updated_at":"2016-08-05T10:54:18Z","closed_at":"2016-08-04T22:12:44Z","body":"I think this is somewhat related to #49...\r\n\r\nWhen you have a repository-based cache it means that you cannot manage separate local object copies that may represent object state for a particular view of the repository. \r\n\r\nIf the cache were managed on a session by session basis, then object lookup and sharing would be guaranteed to be consistent with the db view associated with the session ...\r\n\r\nbesides, sharing common objects between two sessions can get quite confusing ...\r\n\r\nDon't know if this has come up before or not."},"comment":{"url":"https://api.github.com/repos/pharo-nosql/voyage/issues/comments/237821965","html_url":"https://github.com/pharo-nosql/voyage/issues/52#issuecomment-237821965","issue_url":"https://api.github.com/repos/pharo-nosql/voyage/issues/52","id":237821965,"user":{"login":"estebanlm","id":513630,"avatar_url":"https://avatars.githubusercontent.com/u/513630?v=3","gravatar_id":"","url":"https://api.github.com/users/estebanlm","html_url":"https://github.com/estebanlm","followers_url":"https://api.github.com/users/estebanlm/followers","following_url":"https://api.github.com/users/estebanlm/following{/other_user}","gists_url":"https://api.github.com/users/estebanlm/gists{/gist_id}","starred_url":"https://api.github.com/users/estebanlm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/estebanlm/subscriptions","organizations_url":"https://api.github.com/users/estebanlm/orgs","repos_url":"https://api.github.com/users/estebanlm/repos","events_url":"https://api.github.com/users/estebanlm/events{/privacy}","received_events_url":"https://api.github.com/users/estebanlm/received_events","type":"User","site_admin":false},"created_at":"2016-08-05T10:54:18Z","updated_at":"2016-08-05T10:54:18Z","body":"Hi @dalehenrich, \r\nIn fact, caches in voyage are used just to grant object identity... in mongo is centralised because object id are unique in database, not just in collection (this is a consequence of the fact that to this day, mongo cannot give you the id of the inserted object... as it should, IMO, so we calculate them before inserting... an approach that of course has problems, but well, this is like that).\r\nIn UnQLite I choose other approach (keep one cache per collection) because unqlite *does* gives you an id back... but this is collection related so I needed to choose another approach to keep objects... I could have done it different, but this was the easier/faster approach...  in fact I was playing with the idea of also keep collection-based caches in mongo, as I think big weak collections does not behave as fast as smaller ones, then this would be a way to optimise... but anyway, I didn't do anything about, yet :) \r\n"}}
{"actor":{"display_login":"estebanlm"}}