Has anything been written about why we might want to use UnityWebRequest over .NET's own HttpWebRequest (other than the WebGL consideration)?
There doesn't seem to be a lot of information out there about it even though it's slated to no longer be "experimental" in 5.4.
I'm about to start writing a huge number of REST calls and a custom server to process them. I'm deeply familiar with WebRequest and HttpWebRequest but the general lack of concrete information about UnityWebRequest makes me...
UnityWebRequest versus System.Net.HttpWebRequest
There doesn't seem to be a lot of information out there about it even though it's slated to no longer be "experimental" in 5.4.
I'm about to start writing a huge number of REST calls and a custom server to process them. I'm deeply familiar with WebRequest and HttpWebRequest but the general lack of concrete information about UnityWebRequest makes me...
UnityWebRequest versus System.Net.HttpWebRequest