3 Replies Latest reply on Sep 16, 2012 2:28 AM by Magesh Bojan

    Binding UI for HTTP Gateway

    Brian Fitzpatrick Expert

      While working on SWITCHYARD-1027, which is the tooling side of SWITCHYARD-985, I ran into a couple of questions I'm hoping to get some feedback on...

       

      First, here's a screen shot of the UI for an HTTP binding associated with a Service:

      http-binding-service.png

       

      And here's a shot of the HTTP binding associated with a Reference:

      http-binding-reference.png

       

      Not much of a difference other than a few fields (Context Path on the Service side and Operation Selector & Address on the Reference side).

       

      Question #1 - Should I make Method field a drop-down list with the common HTTP methods? (GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE, CONNECT) If I go that route does it need to be editable?

       

      Question #2 - Should I make the Content Type field an editable drop-down list with some common content types? This seems largely impossible unless we limit it to a few common text types (http://en.wikipedia.org/wiki/MIME_type).

       

      Or should I leave them both just as plain text fields folks can enter anything into?

       

      Thanks in advance.