WP7后台线程
WP7 中的线程是否存在于整个应用程序中，还是仅限于一个页面？ 假设我开始在一个页面上下载，该页面像往常一样由后台线程处理，并且其进度由状态栏更新。现在用户希望使用应用程序的其他方面。如果他使用应用程序栏控件或后退按钮导航到另一个页面，后台线程会死掉吗？如果不是，关于仅用于下载的后台线程的好习惯是什么...就像它们可以存在于应用程序中一样，是否应该在应用程序启动时启动它们并等待下载队列有一个请求排队？
谢谢
-埃贡
Are the threads in a WP7, exist across the app, or are they confined to a page ?
Say I started download on a page, which is being handled by a background thread as usual, and its progress is being updated by a status bar. Now the user wishes to use other aspects of the application. Will the background thread die if he navigates to another page, either using Application bar controls or back button, to a page within the app ? If not what is a good practice regarding background thread dedicated only to downloads... like if they can exist across the app, should they be initiated when the app is initiated and made to wait until the download queue has a request queued up ?
Thnx
-Egon
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您有一个纯粹致力于下载外部资源的线程，我会在应用程序级别启动该线程。线程应该报告进度/完成/等等。到应用程序级别对象而不是特定页面。如果页面需要显示详细信息，则应查询应用程序级别对象。这样，页面之间的交互将不会产生任何影响，并且数据（例如下载进度）将始终可供任何页面需要。
我唯一可以在页面级别执行此操作的情况是应用程序仅包含单个页面，但这几乎是同一件事。
If you have a thread that is purely dedicated to downloading an external resource I'd launch this thread at application level. The thread shoudl report progress/completion/etc. to an application level object and not to a specific page. The page shoudl query the app level object if it needs details to display. This way the interactions between pages will have no effect and the data (e.g. download progress) will always be available to whatever page wants it.
The only time I may do this at a page level is if the app only contained a single page but then that's pretty much just the same thing.