)]}'
{"oslo_messaging/notify/notifier.py":[{"author":{"_account_id":8770,"name":"Ken Giusti","email":"kgiusti@gmail.com","username":"kgiusti"},"change_message_id":"9a88da31fb42c9e53a781981a9fc2cb95e7b533c","unresolved":false,"context_lines":[{"line_number":138,"context_line":""},{"line_number":139,"context_line":"def get_notification_transport(conf, url\u003dNone,"},{"line_number":140,"context_line":"                               allowed_remote_exmods\u003dNone, aliases\u003dNone):"},{"line_number":141,"context_line":"    \"\"\"A factory method for Transport objects for notifications."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"    If no transport URL is provided, the URL in the notifications section of"},{"line_number":144,"context_line":"    the config file will be used.  If that URL is also absent, the same"}],"source_content_type":"text/x-python","patch_set":1,"id":"3ac371cc_729fc103","line":141,"updated":"2016-08-15 14:48:49.000000000","message":"Looks good, but can you add a bit of description as to why one would use get_notification_transport instead of just get_transport?   Something like:\n\n\"This method allows notification messages to use a different driver than the driver used for RPC.  For example an application may use the ZeroMQ driver for RPC messages while using the RabbitMQ driver for notification messages.\"","commit_id":"7405a5543861f95ebe1066d67a6a2fe4910d919d"}]}