)]}'
{"specs/backlog/resource-object-refactor.rst":[{"author":{"_account_id":6484,"name":"Feilong Wang","email":"hustemb@gmail.com","username":"flwang"},"change_message_id":"54860befb36bd5c973cdf572f10feb2fea2352d9","unresolved":false,"context_lines":[{"line_number":39,"context_line":"for some internal usage. Their keyts are started with a \"_\". The keys are"},{"line_number":40,"context_line":"specified and can\u0027t be changed or used for other purpose. Now it includes:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- ``_max_messages_post_size``: The max post size of messages defined for a"},{"line_number":43,"context_line":"  queue."},{"line_number":44,"context_line":"  **Default value**: CONF.transport.max_messages_post_size"},{"line_number":45,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_75b47dd1","line":42,"updated":"2017-11-17 01:48:54.000000000","message":"I don\u0027t have a clear idea yet. But the rough idea in my mind now is:\n\n1. If the key is introduced by a feature, like dead letter queue or flavor, then it should be an attribute of the queue.\n\n2. If the key is related to the queue itself, like \u0027max_message_post_size\u0027, it\u0027s completely independent of the messaging service. In other words, if the queue is moved from our system to another services, like SQS, those metadata will be kept anyway.","commit_id":"2f9e9f9a4168203b3053e696f3e562797fa60cf2"}]}