Hi,
I implemented REST calls with the experimental UnityWebRequest using https and the 4 common verbs (GET, POST, PUT, and DELETE) and it seems to work pretty well.
Considering that the class is located in an experimental namespace, I’m concerned to use it in a real solution.
Moreover, it is not yet supported on PS4.
When do you expect to release it officially on Windows?
When do you expect to release a beta version on PS4?
Thank you!
Michael
Im looking into the same info.
After release (I think it was on september?), UnityWebRequest is not detailed anywhere else in the engine Roadmap page, and Im wondering what are the nexts steps, so I can take more informed decisions about porting from WWW to UnityWebRequest or wait until is graduated from ‘Experimental’.
Is there a timeline?
Also, what are the plans for WWW class, is going to be deprecated?
Thanks 
UnityWebRequest is being promoted to Networking namespace as-we-speak. I already commited all the necessary changes.
As for PS4, this backend is already implemented, and the implementation will be merged to 5.4 later this month or in the beginning of December.
[Edit: As for WWW, you have correctly surmised that this class is going to be deprecated. I cannot give a timeline set in stone, but I would expect it to be marked as being deprecated in 5.4, and then actively removed in, say, 5.6. But I reiterate that the timeline is not set in stone.]
On the topic of UnityWebRequest:
This is great.
Any chance to have some example of this REST implementation?
It looks like Unity 5.3 was released and UnityWebRequest remains as experimental.
Also, I have opened a few cases in the issue manager regarding bugs on UnityWebRquest.
Any comments on what to expect?
There are also a few bug cases raised, although Im not sure who is in charge of the UnityWebRequest api, and not even sure where to post about it. Scripting forum? Networking forum?
There is an awkward grey zone around this.
Perhaps I should have been a bit more clear. UnityWebRequest is no longer experimental in 5.4. As for 5.3, it’s still being kept in Experimental namespace.
Hello @Justinas , happy new year.
Thank you very much for the clarification, indeed it sounded to me like that namespace promotion was going to be part of point release 3.
There are some bugs and issues I found on the new API, would you take a look? I have an asset store extension that highly depends on what happens to this API, but Im completely blindfolded about timelines, bug fixing, etc.
Hi.
@Justinas I’m having a problem setting “cookie” header using SetRequestHeader , I read in another post that you were working that out last year, is that a bug?