├── .gitignore ├── LICENSE ├── README.md └── status_change.png /.gitignore: -------------------------------------------------------------------------------- 1 | # Xcode 2 | # 3 | build/ 4 | *.pbxuser 5 | !default.pbxuser 6 | *.mode1v3 7 | !default.mode1v3 8 | *.mode2v3 9 | !default.mode2v3 10 | *.perspectivev3 11 | !default.perspectivev3 12 | xcuserdata 13 | *.xccheckout 14 | *.moved-aside 15 | DerivedData 16 | *.hmap 17 | *.ipa 18 | *.xcuserstate 19 | 20 | # CocoaPods 21 | # 22 | # We recommend against adding the Pods directory to your .gitignore. However 23 | # you should judge for yourself, the pros and cons are mentioned at: 24 | # http://guides.cocoapods.org/using/using-cocoapods.html#should-i-ignore-the-pods-directory-in-source-control 25 | # 26 | #Pods/ 27 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "{}" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright {yyyy} {name of copyright owner} 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | 203 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 续言关于下载管理的探讨 2 | 3 | 4 | * 继上次发博（），叙述实现项目下载管理时遇到的种种问题，以及应对之策后，不少大神纷纷指出，笔者的用法可能不太对，没有细读源码等等。可遗憾的是，批评过后，却始终无人提出一套完整有效的解决方案来处理下载管理的需求。实际上这个才是重点中的重点啊！可惜抛砖引玉未能成功😂。笔者现把个人认为理想的下载任务管理的模型整理如下，期待能有大神给予完美的实现，供更多开发者学习交流。 5 | 6 | --- 7 | * 首先，理想的解决方案，应当使每个下载任务各自作为一个实体对象，而这样的一个对象起码应当至少有如下几个最最基本的属性： 8 | 9 | 1. 下载任务的标示id 10 | 2. 下载的进度（只读） 11 | 3. 下载任务的状态（只读） 👀 12 | 4. 下载资源的URL地址 13 | 5. 下载到本地的保存地址 14 | 6. 下载任务的创立时间 15 | 7. 下载任务的完成时间 16 | 8. ...... 17 | (其中下载任务的状态，应当至少分为六种：待续状态、正在执行状态、暂停状态、中途失败状态、自然完成状态、被取消状态) 18 | * 其次，这个下载任务对象还应该有相应的方法或途径，实现如图所示的六种状态间的转换 19 | ![status_change](status_change.png) 20 | `（其中红色箭头表示笔者认为倘使用AFHTTPRequestOperation是没有直接途径或不易做到的转换）` 21 | 22 | 理由即为需求，其中最棘手的一点常是： 23 | 24 | 往往会有规定，队列最多允许有多少个任务同时处于正在下载的状态中。因此我们在将某个暂停或中途失败的任务恢复时，就不能认为只需将其恢复至正在执行中的状态就OK了，而应当根据队列中正在执行的下载任务的数量，决定是将其恢复至正在执行的状态，还是等待就绪的状态 25 | 26 | 总结上图，下载任务在处于不同的状态时，应当分别能够做到如下所列的几种行为 27 | 28 | 1. 处于待续状态时，可手动启动该任务，或直接将该任务取消，移出下载队列 29 | 2. 处于正在执行状态时，可使该任务暂停，或恢复至待续状态，或直接将该任务取消，移出下载队列，或由其自身转变为自然完成/下载中途失败的状态 30 | 3. 处于暂停状态时，可使之恢复至待续状态/正在执行状态，或直接将该任务取消，移出下载队列 31 | 4. 处于下载中途失败的状态时，可使之恢复至待续状态/正在执行状态，或直接将该任务取消，移出下载队列（基本要跟处于暂停状态时能够做到的事情一样） 32 | 5. 处于被取消状态或自然完成后的状态时，可以不需要有向其它状态转换的方式 33 | 34 | * 这个对象还应当有在下载被启动时（不仅手动启动，还可能是在队列中轮到了该任务），下载进度发生变化时，下载自然完成时，下载中途失败时的自动调用回调方法；或能够做到对下载进度、下载任务状态变化的KVO亦可 35 | 36 | * 这个对象应当能够便利于下载任务的启动及恢复重建 37 | 38 | * 这个对象还应有方便于本地持久化储存的能力，如可以实现NSCoding协议之类 39 | 40 | * ......其它能够使得下载任务变得更加高效的特性 41 | 42 | --- 43 | * 其次是下载队列，应当具备如下特性： 44 | 45 | 1. 通常的需求，存在于下载队列中归其管理的任务，应当是处于这四种状态的：待续状态、正在执行状态、暂停状态、中途失败状态；而处于自然完成状态、被取消状态的任务，应当不被包含在下载队列当中 46 | 2. 这个队列当中，除当任务自然完成，或被人为取消时，要将该任务移除队列以外，不能因为其中任何任务的任何状态的变化而改变它们之间的相互顺序 47 | 3. 这个队列要能够控制同时处于正在执行状态的下载任务的最大个数，这就意味着当队列中的某一个任务从正在执行状态变为其它非待续状态的状态之后，就要检测队列中还有无处于待续状态的任务，并启动之，以补充同时正在执行的下载任务的数量 48 | 4. 下载队列的顺序应当能够通过某种方式进行本地的持久化存储 49 | 5. ......其它能够使得下载管理变得更加高效的特性 50 | 51 | --- 52 | * 以上是笔者认为最合理的下载管理解决方案应具备的特性。笔者承认自己才疏学浅，当前项目所使用方案确有甚多不尽完美之处，不值得向广大开源社区进行推广。现仅想以这两篇浅陋博文为砖，引来大神诠释完美技术手段，以实现上述理想中的需求。笔者愿洗耳恭听，以解心中疑惑，感念之情溢于言表 -------------------------------------------------------------------------------- /status_change.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/DeveloperLx/Dreamy_download_manage_solution/66ca403be762363b0915b5992a19d77f54a4371b/status_change.png --------------------------------------------------------------------------------