{"action":"created","issue":{"url":"https://api.github.com/repos/cerebris/jsonapi-resources/issues/583","labels_url":"https://api.github.com/repos/cerebris/jsonapi-resources/issues/583/labels{/name}","comments_url":"https://api.github.com/repos/cerebris/jsonapi-resources/issues/583/comments","events_url":"https://api.github.com/repos/cerebris/jsonapi-resources/issues/583/events","html_url":"https://github.com/cerebris/jsonapi-resources/issues/583","id":125265526,"number":583,"title":"Cross-resource parameters:  Custom HTTP headers or JSONAPI meta","user":{"login":"bjubinville","id":130537,"avatar_url":"https://avatars.githubusercontent.com/u/130537?v=3","gravatar_id":"","url":"https://api.github.com/users/bjubinville","html_url":"https://github.com/bjubinville","followers_url":"https://api.github.com/users/bjubinville/followers","following_url":"https://api.github.com/users/bjubinville/following{/other_user}","gists_url":"https://api.github.com/users/bjubinville/gists{/gist_id}","starred_url":"https://api.github.com/users/bjubinville/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bjubinville/subscriptions","organizations_url":"https://api.github.com/users/bjubinville/orgs","repos_url":"https://api.github.com/users/bjubinville/repos","events_url":"https://api.github.com/users/bjubinville/events{/privacy}","received_events_url":"https://api.github.com/users/bjubinville/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-06T21:19:42Z","updated_at":"2016-01-12T21:16:21Z","closed_at":"2016-01-12T21:16:21Z","body":"Hi,\r\n\r\nThis isn't necessarily a question specific about jsonapi-resources, but figured since this community was so awesome, I'd ask for some feedback here.\r\n\r\nIn most of the APIs I've built, I've had a requirement to pass \"global\" configuration parameters that have been required for proper request processing.  Historically I've used custom HTTP headers with a serialized json object.  This has worked well, and I'm not one to stand on ceremony on the \"correctness\" in this.  It works.\r\n\r\nThat said, I thought it was worth asking if `meta` is a decent place to hang these kinds of cross-resource parameters.  I like the idea of being able to reconstruct a request just from the payload and not have to go searching for headers etc.  Validation of these parameters may also be a little easier as well.  It certainly would be an abuse of the spec to lean on this however: http://jsonapi.org/format/#document-meta.\r\n\r\nAny thoughts or comments?  \r\n\r\nAs always, many thanks for the community's insights."},"comment":{"url":"https://api.github.com/repos/cerebris/jsonapi-resources/issues/comments/171057113","html_url":"https://github.com/cerebris/jsonapi-resources/issues/583#issuecomment-171057113","issue_url":"https://api.github.com/repos/cerebris/jsonapi-resources/issues/583","id":171057113,"user":{"login":"bjubinville","id":130537,"avatar_url":"https://avatars.githubusercontent.com/u/130537?v=3","gravatar_id":"","url":"https://api.github.com/users/bjubinville","html_url":"https://github.com/bjubinville","followers_url":"https://api.github.com/users/bjubinville/followers","following_url":"https://api.github.com/users/bjubinville/following{/other_user}","gists_url":"https://api.github.com/users/bjubinville/gists{/gist_id}","starred_url":"https://api.github.com/users/bjubinville/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bjubinville/subscriptions","organizations_url":"https://api.github.com/users/bjubinville/orgs","repos_url":"https://api.github.com/users/bjubinville/repos","events_url":"https://api.github.com/users/bjubinville/events{/privacy}","received_events_url":"https://api.github.com/users/bjubinville/received_events","type":"User","site_admin":false},"created_at":"2016-01-12T21:16:21Z","updated_at":"2016-01-12T21:16:21Z","body":"After mulling over the spec and the intentions behind `meta` as it stands now, I'm going to stick with custom HTTP header usage. "}}