- From: Manu Sporny <notifications@github.com>
- Date: Wed, 20 Jan 2016 20:05:41 -0800
- To: w3c/webpayments <webpayments@noreply.github.com>
Received on Thursday, 21 January 2016 04:06:36 UTC
Let's also not forget that XMLHttpRequest is problematic API partially due to the fact that it stores state (like the PaymentRequest API proposal) and managing that state machine has led to code being more complicated than necessary for developers. The problem got so bad that there is a new Fetch API proposal that attempts to cut down on many of the state-machine related issues (among a slew of other non-state-machine-related issues). --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/36#issuecomment-173445535
Received on Thursday, 21 January 2016 04:06:36 UTC