当您将二进制文件上传到 Apple 的 iTunesConnect 时会发生什么？
编辑：...我问是因为：它可能表明我们可以采取一些措施来加快这一过程。
大约一年前，这个过程从“由于苹果服务器功率不足而缓慢”变成了“非常慢，因为苹果使用了发送二进制文件所需带宽的 3 倍”。
例如，我最近提交了一个 90Mb 的应用程序，Xcode4 向 Apple 上传了超过 350Mb 的数据。
例如，刚才我提交了一个8Mb的二进制文件，Xcode4向Apple上传了超过40Mb的数据。
最近上传器有了很大的改进（例如，在上面的其中一个上传过程中，我中途失去了 DSL 连接。Apple 花了大约 30 秒的时间才恢复并恢复上传 - 但以前的版本在这种情况下只会崩溃）。
但我想知道：苹果在上传过程中实际上在做什么？该进程在我们的本地计算机上运行 - 有人尝试过查看网络流量吗？还是在流程中？
我看到了几个不同的阶段，只是通过监视“ps”：
- unzip（用于重新进行代码签名）
- codesign（同上）
- Java（我相信用于上传器接口）
- 然后ascp（Apple SCP，我猜？ ）
EDIT: ...and I'm asking because: it might point to things we can do to speed-up the process.
About a year ago, this process went from being "slow because Apple's servers were under-powered" to being "very slow because Apple used 3 times the bandwidth required to send the binary".
e.g. I submitted a 90Mb app recently, and Xcode4 uploaded over 350Mb of data to Apple.
e.g. just now I submitted an 8Mb binary, and Xcode4 uploaded over 40Mb of data to Apple.
There have been big improvements in the uploader recently (e.g. during one of those uploads above, I lost DSL connection partway. It took Apple about 30 seconds to recover and resume the upload - but previous versions would just crash in that scenario).
But I'm wondering: what is Apple actually doing during upload? The process runs on our local machines - has anyone tried peeking at the net traffic? or at the processes?
I saw a couple of different phases, just by monitoriing 'ps':
- unzip (for re-doing the code signing)
- codesign (ditto)
- Java (for the uploader interface, I believe)
- then ascp (Apple SCP, I'm guessing?)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
推测：它使用与 Finder 相同的 WebDAV 实现，但速度非常慢。
Speculation: it uses the same WebDAV implementation as Finder, which is very slow.