{"action":"created","issue":{"url":"https://api.github.com/repos/trellis-ldp/trellis/issues/300","repository_url":"https://api.github.com/repos/trellis-ldp/trellis","labels_url":"https://api.github.com/repos/trellis-ldp/trellis/issues/300/labels{/name}","comments_url":"https://api.github.com/repos/trellis-ldp/trellis/issues/300/comments","events_url":"https://api.github.com/repos/trellis-ldp/trellis/issues/300/events","html_url":"https://github.com/trellis-ldp/trellis/issues/300","id":381680787,"node_id":"MDU6SXNzdWUzODE2ODA3ODc=","number":300,"title":"\"Live\"ness in different places","user":{"login":"ajs6f","id":110994,"node_id":"MDQ6VXNlcjExMDk5NA==","avatar_url":"https://avatars1.githubusercontent.com/u/110994?v=4","gravatar_id":"","url":"https://api.github.com/users/ajs6f","html_url":"https://github.com/ajs6f","followers_url":"https://api.github.com/users/ajs6f/followers","following_url":"https://api.github.com/users/ajs6f/following{/other_user}","gists_url":"https://api.github.com/users/ajs6f/gists{/gist_id}","starred_url":"https://api.github.com/users/ajs6f/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ajs6f/subscriptions","organizations_url":"https://api.github.com/users/ajs6f/orgs","repos_url":"https://api.github.com/users/ajs6f/repos","events_url":"https://api.github.com/users/ajs6f/events{/privacy}","received_events_url":"https://api.github.com/users/ajs6f/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-16T16:54:36Z","updated_at":"2018-11-16T17:45:27Z","closed_at":null,"author_association":"MEMBER","body":"Currently, Trellis has no overall policy about the \"live\"ness of data, but in several implementations, we've independently chosen to have metadata in state in `Resource` impls, but tuples come \"live\".\r\n\r\nSuppose at t=0 I call `Resource:Service::get` and then hold onto my `Resource` until t=2 before calling `stream` on it. In the meantime, at t=1, another request completes to alter that resource. Now the original client is getting metadata from t=0 and quads from t=1.\r\n\r\nProblem?"},"comment":{"url":"https://api.github.com/repos/trellis-ldp/trellis/issues/comments/439471615","html_url":"https://github.com/trellis-ldp/trellis/issues/300#issuecomment-439471615","issue_url":"https://api.github.com/repos/trellis-ldp/trellis/issues/300","id":439471615,"node_id":"MDEyOklzc3VlQ29tbWVudDQzOTQ3MTYxNQ==","user":{"login":"ajs6f","id":110994,"node_id":"MDQ6VXNlcjExMDk5NA==","avatar_url":"https://avatars1.githubusercontent.com/u/110994?v=4","gravatar_id":"","url":"https://api.github.com/users/ajs6f","html_url":"https://github.com/ajs6f","followers_url":"https://api.github.com/users/ajs6f/followers","following_url":"https://api.github.com/users/ajs6f/following{/other_user}","gists_url":"https://api.github.com/users/ajs6f/gists{/gist_id}","starred_url":"https://api.github.com/users/ajs6f/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ajs6f/subscriptions","organizations_url":"https://api.github.com/users/ajs6f/orgs","repos_url":"https://api.github.com/users/ajs6f/repos","events_url":"https://api.github.com/users/ajs6f/events{/privacy}","received_events_url":"https://api.github.com/users/ajs6f/received_events","type":"User","site_admin":false},"created_at":"2018-11-16T17:45:27Z","updated_at":"2018-11-16T17:45:27Z","author_association":"MEMBER","body":"I'm thinking of multiple (JVM) clients to the service, not multiple (HTTP) clients to the server, but if we just want to rule that out (declare that any `ResourceService` instance is usable only from some well-defined scope that presumably be in-JVM), that works for me."}}
{"actor":{"display_login":"ajs6f"}}