![\"\"](\"https:\/\/demensdeum.com\/blog\/wp-content\/uploads\/2019\/06\/bridge.jpg\")
<\/p>\nLe mod\u00e8le Bridge fait r\u00e9f\u00e9rence \u00e0 des mod\u00e8les de conception structurelle. Il vous permet d’abstraire l’impl\u00e9mentation de la logique de classe en d\u00e9pla\u00e7ant la logique dans une classe abstraite distincte. Cela semble simple, n’est-ce pas\u00a0?<\/p>\n
<\/p>\n
Supposons que nous impl\u00e9mentions un robot spam capable d’envoyer des messages \u00e0 diff\u00e9rents types de messagers.
Nous l’impl\u00e9mentons en utilisant un protocole commun\u00a0:<\/p>\n
protocol User {\n let token: String\n let username: String\n}\n\nprotocol Messenger {\n var authorize(login: String, password: String)\n var send(message: String, to user: User)\n}\n\nclass iSeekUUser: User {\n let token: String\n let username: String\n}\n\nclass iSeekU: Messenger {\n\n var authorizedUser: User?\n var requestSender: RequestSender?\n var requestFactory: RequestFactory?\n\n func authorize(login: String, password: String) {\n authorizedUser = requestSender?.perform(requestFactory.loginRequest(login: login, password: password))\n }\n \n func send(message: String, to user: User) {\n requestSender?.perform(requestFactory.messageRequest(message: message, to: user)\n }\n}\n\nclass SpamBot {\n func start(usersList: [User]) {\n let iSeekUMessenger = iSeekU()\n iSeekUMessenger.authorize(login: \"SpamBot\", password: \"SpamPassword\")\n \n for user in usersList {\n iSeekUMessennger.send(message: \"Hey checkout demensdeum blog! http:\/\/demensdeum.com\", to: user)\n }\n }\n}\n<\/code><\/pre>\n<\/div>\nImaginons maintenant la sortie d’un nouveau protocole plus rapide pour envoyer des messages pour le messager iSekU. Pour ajouter un nouveau protocole, vous devrez dupliquer l’impl\u00e9mentation du bot iSekU, en n’en modifiant qu’une petite partie. On ne sait pas pourquoi faire cela si seulement une petite partie de la logique de classe a chang\u00e9. Avec cette approche, le principe DRY est viol\u00e9\u00a0; avec le d\u00e9veloppement ult\u00e9rieur du produit, le manque de flexibilit\u00e9 se fera sentir par des erreurs et des retards dans la mise en \u0153uvre de nouvelles fonctionnalit\u00e9s.
D\u00e9pla\u00e7ons la logique du protocole dans une classe abstraite, impl\u00e9mentant ainsi le mod\u00e8le Bridge\u00a0:<\/p>\n
\nprotocol User {\n let token: String\n let username: String\n}\n\nprotocol Messenger {\n var authorize(login: String, password: String)\n var send(message: String, to user: User)\n}\n\nprotocol MessagesSender {\n func send(message: String, to user: User)\n}\n\nclass iSeekUUser: User {\n let token: String\n let username: String\n}\n\nclass iSeekUFastMessengerSender: MessagesSender {\n func send(message: String, to user: User) {\n requestSender?.perform(requestFactory.messageRequest(message: message, to: user)\n }\n}\n\nclass iSeekU: Messenger {\n\n var authorizedUser: User?\n var requestSender: RequestSender?\n var requestFactory: RequestFactory?\n var messagesSender: MessengerMessagesSender?\n\n func authorize(login: String, password: String) {\n authorizedUser = requestSender?.perform(requestFactory.loginRequest(login: login, password: password))\n }\n \n func send(message: String, to user: User) {\n messagesSender?.send(message: message, to: user)\n }\n}\n\nclass SpamBot {\n\n var messagesSender: MessagesSender?\n\n func start(usersList: [User]) {\n let iSeekUMessenger = iSeekU()\n iSeekUMessenger.authorize(login: \"SpamBot\", password: \"SpamPassword\")\n \n for user in usersList {\n messagesSender.send(message: \"Hey checkout demensdeum blog! http:\/\/demensdeum.com\", to: user)\n }\n }\n}\n<\/code><\/pre>\n<\/div>\nL’un des avantages de cette approche est sans aucun doute la possibilit\u00e9 d’\u00e9tendre les fonctionnalit\u00e9s de l’application en \u00e9crivant des plugins\/biblioth\u00e8ques qui impl\u00e9mentent une logique abstraite sans changer le code de l’application principale.
Quelle est la diff\u00e9rence avec le mod\u00e8le Strat\u00e9gie ? Les deux mod\u00e8les sont tr\u00e8s similaires, cependant, Strategy d\u00e9crit la commutation d’*algorithmes*, tandis que Bridge vous permet de changer de grandes parties de *n’importe quelle logique complexe*.<\/p>\n
Sources<\/h3>\n
https:\/\/refactoring.guru\/ru\/design-patterns\/bridge <\/a><\/p>\nCode source<\/h3>\n
https:\/\/gitlab.com\/demensdeum\/patterns\/<\/a><\/ une> p><\/p>\n","protected":false},"excerpt":{"rendered":"Le mod\u00e8le Bridge fait r\u00e9f\u00e9rence \u00e0 des mod\u00e8les de conception structurelle. Il vous permet d’abstraire l’impl\u00e9mentation de la logique de classe en d\u00e9pla\u00e7ant la logique dans une classe abstraite distincte. Cela semble simple, n’est-ce pas\u00a0? Supposons que nous impl\u00e9mentions un robot spam capable d’envoyer des messages \u00e0 diff\u00e9rents types de messagers.Nous l’impl\u00e9mentons en utilisant unContinue reading “Pont \u00e0 motifs”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[61,52],"tags":[106,95],"class_list":["post-2042","post","type-post","status-publish","format-standard","hentry","category-techie","category-tutorials","tag-bridge","tag-patterns","entry"],"translation":{"provider":"WPGlobus","version":"3.0.2","language":"fr","enabled_languages":["en","ru","zh","de","fr","ja","pt"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"ru":{"title":true,"content":true,"excerpt":false},"zh":{"title":true,"content":true,"excerpt":false},"de":{"title":true,"content":true,"excerpt":false},"fr":{"title":true,"content":true,"excerpt":false},"ja":{"title":true,"content":true,"excerpt":false},"pt":{"title":true,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/posts\/2042","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/comments?post=2042"}],"version-history":[{"count":12,"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/posts\/2042\/revisions"}],"predecessor-version":[{"id":3955,"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/posts\/2042\/revisions\/3955"}],"wp:attachment":[{"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/media?parent=2042"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/categories?post=2042"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/fr\/wp-json\/wp\/v2\/tags?post=2042"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}