Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: Unknown
    • Labels:
      None
    • Rice Theme:
      Service Orientation
    • Priority Score:
      0
    • Functional Justification :
      Hide
      REST is an alternative to SOAP-based web services. It uses the HTTP protocol and it's various "verbs" like GET, POST, PUT, DELETE, HEAD, etc. The payload can be anything you want though it's typically either XML or JSON (JSON is becoming the preferred format these days). In SOAP web services, it can only be XML. This can be a big benefit to implementors in that it makes things more flexible since they aren't limited to only XML as they work towards integration with Rice. It's important to note that REST is not a standard but rather an "architectural style".

      Currently Rice offers services, how an application calls functionality in Rice, using an older service method of SOAP. Technology has move forward and leading applications are offering REST services, many will consider an out of date framework due to it's use of SOAP only. REST uses standard HTTP and is a simpler in just about every way; creating clients, developing APIs, etc. In general, with REST, performance is also better and scalability is improved.
      Show
      REST is an alternative to SOAP-based web services. It uses the HTTP protocol and it's various "verbs" like GET, POST, PUT, DELETE, HEAD, etc. The payload can be anything you want though it's typically either XML or JSON (JSON is becoming the preferred format these days). In SOAP web services, it can only be XML. This can be a big benefit to implementors in that it makes things more flexible since they aren't limited to only XML as they work towards integration with Rice. It's important to note that REST is not a standard but rather an "architectural style". Currently Rice offers services, how an application calls functionality in Rice, using an older service method of SOAP. Technology has move forward and leading applications are offering REST services, many will consider an out of date framework due to it's use of SOAP only. REST uses standard HTTP and is a simpler in just about every way; creating clients, developing APIs, etc. In general, with REST, performance is also better and scalability is improved.
    • Impact if not Implemented:
      Without this [now] commonly desired service option, Rice will be viewed as archaic compared to other solutions in this space. Rice will be more difficult to integrate with.
    • Priority - KFS:
      No Priority
    • Priority - KC:
      No Priority
    • Priority - KS:
      No Priority
    • Priority - Rice:
      No Priority
    • Effort Estimate:
      High ~ 1000 hrs

      Description

      Update Rice to offer REST versions of our services in addition to how we currently offer our services.

        Attachments

          Issue Links

            Activity

            Hide
            ewestfal Eric Westfall added a comment -

            Assigning myself in order to champion this item.

            Show
            ewestfal Eric Westfall added a comment - Assigning myself in order to champion this item.

              People

              • Assignee:
                ewestfal Eric Westfall
                Reporter:
                masargen Matt Sargent
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: