Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

UnityWebRequest roadmap

Discussion in 'Scripting' started by michael.catanzariti, Nov 8, 2015.

  1. michael.catanzariti

    michael.catanzariti

    Joined:
    Aug 25, 2015
    Posts:
    2
    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
     
    kshaja and Novack like this.
  2. Novack

    Novack

    Joined:
    Oct 28, 2009
    Posts:
    840
    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 :)
     
    Last edited: Dec 1, 2015
  3. Justinas

    Justinas

    Unity Technologies

    Joined:
    Sep 25, 2013
    Posts:
    12
    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.]
     
    Novack likes this.
  4. Chris-HG

    Chris-HG

    Joined:
    Aug 10, 2012
    Posts:
    63
    On the topic of UnityWebRequest:

    * POST
    - add override to accept raw byte[]
    - allow POST and PUT with 0 byte or null payload​
    * Status Code != 200
    - return body when status code is not 200​
     
  5. kshaja

    kshaja

    Joined:
    Sep 22, 2010
    Posts:
    148
    This is great.
    Any chance to have some example of this REST implementation?
     
  6. Novack

    Novack

    Joined:
    Oct 28, 2009
    Posts:
    840
    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?
     
  7. Novack

    Novack

    Joined:
    Oct 28, 2009
    Posts:
    840
    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.
     
  8. Justinas

    Justinas

    Unity Technologies

    Joined:
    Sep 25, 2013
    Posts:
    12
    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.
     
  9. Novack

    Novack

    Joined:
    Oct 28, 2009
    Posts:
    840
    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.
     
  10. MarioRuiz

    MarioRuiz

    Joined:
    Nov 7, 2009
    Posts:
    161
    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?