aboutsummaryrefslogtreecommitdiffstats
path: root/components/layout/construct.rs
diff options
context:
space:
mode:
authorbors-servo <lbergstrom+bors@mozilla.com>2016-03-02 01:49:29 +0530
committerbors-servo <lbergstrom+bors@mozilla.com>2016-03-02 01:49:29 +0530
commit22ce878edc22360af7391694efc9e5668116d3fb (patch)
treedf9edf8a1b55da1891087fea63ee741cdd98b171 /components/layout/construct.rs
parentb355c0dbcbbbb5155170b4db971e012659081843 (diff)
parent3f79667050cb1afe39d912900a0f365ddabd20e2 (diff)
downloadservo-22ce878edc22360af7391694efc9e5668116d3fb.tar.gz
servo-22ce878edc22360af7391694efc9e5668116d3fb.zip
Auto merge of #9753 - nikkisquared:async_fetch, r=jdm
Make Fetch Protocol Asynchronous I'm working on making it possible to run Fetch Asynchronously, as required for some steps, such as Main Fetch. It looks like somebody has already laid some groundwork for that, with a AsyncFetchListener trait and two async fetch functions defined, which I'm building on top of. So far, as a sort of proof of concept, I've written a test to asynchronously retrieve a fetch response, which uses a simple function to check if the fetch response is complete or not. I'd like to be checked if I'm on the right path, to see if I need to rework anything so far, and what my next step can be. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.svg" height="40" alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9753) <!-- Reviewable:end -->
Diffstat (limited to 'components/layout/construct.rs')
0 files changed, 0 insertions, 0 deletions