)]}'
{"swift/common/middleware/tempauth.py":[{"author":{"_account_id":2696,"name":"Darrell Bishop","email":"dbishop@nvidia.com","username":"darrellb"},"change_message_id":"47ff2bb70e0e4a1b992f595ebe69f22785c3c8c3","unresolved":false,"context_lines":[{"line_number":67,"context_line":"    :param conf: The dict of configuration values"},{"line_number":68,"context_line":"    \"\"\""},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"    @classmethod"},{"line_number":71,"context_line":"    def acl_list_to_header(self, acl_list):"},{"line_number":72,"context_line":"        \"\"\""},{"line_number":73,"context_line":"        Return tempauth\u0027s encoding of a list representing an ACL."}],"source_content_type":"text/x-python","patch_set":9,"id":"AAAATn%2F9mKg%3D","line":70,"updated":"2013-12-09 20:43:21.000000000","message":"What do you think about sticking acl_list_to_header(), header_to_acl_list(), and account_acls() in some utility module?\n\nThe first two don\u0027t use their class argument (which is assigned to a variable called \"self\") and the third only uses its object instance to call those class methods.\n\nMaybe swift.common.request_helpers?","commit_id":"224291ef703a76077e7d897153e0c1840bc17e1f"},{"author":{"_account_id":8262,"name":"Jon Snitow","email":"otherjon@swiftstack.com","username":"otherjon"},"change_message_id":"fc1968fbfb56dee57ff6c7d98faadd0fd296a62c","unresolved":false,"context_lines":[{"line_number":67,"context_line":"    :param conf: The dict of configuration values"},{"line_number":68,"context_line":"    \"\"\""},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"    @classmethod"},{"line_number":71,"context_line":"    def acl_list_to_header(self, acl_list):"},{"line_number":72,"context_line":"        \"\"\""},{"line_number":73,"context_line":"        Return tempauth\u0027s encoding of a list representing an ACL."}],"source_content_type":"text/x-python","patch_set":9,"id":"AAAATn%2F9mIg%3D","line":70,"in_reply_to":"AAAATn%2F9mKg%3D","updated":"2013-12-09 21:15:08.000000000","message":"I\u0027m not strongly against it, but I wanted the code structure to emphasize that the authority and responsibility for defining the header format (serialization, capabilities, field names, etc.) lies with the auth system.  Tempauth makes the choices shown here (JSON-serialized list of strings), but any other auth system is free to make other choices.\n\nThoughts?","commit_id":"224291ef703a76077e7d897153e0c1840bc17e1f"}]}
