Skip to Content

Proprietary channels vs open HTTP channel

This Document tries to highlight the advantages of using open ODP HTTP channel over any proprietary channel.

Introduction to http channel

HTTP channel supports open standards by exposing SUP Online services as OData services which can be consumed by application over native http(s) communication. This openness also enables browser based applications to use this channel. SUP acts as an OData provider, the client will only contact SUP which in turn will get data from backend server. To achieve this SUP will support URL Re-write where by all backend server URLs will be rewritten with SUP URLs allowing clients to make direct http calls with functional URLs. SUP runtime will replace the requisites with backend server information and forward to backend server.

Also to support additionally non-O-Data backends like DOE, MOBI, custom headers on this channel can be used whereby SUP can allow proxy calls without URL Rewrite.

SUP 2.2 Server supports SSL over HTTP to provide secure communication between client and SUP server. Any client application can open a secure http(s)   connection with SUP and utilize it for proxy services. Application will have to take care of enabling https at their end and accept the server identity certificate and store in the client trust store.  SUP will provide Both Single SSL and Strong mutual SSL over HTTP. Applications can choose either of the one to connect to server.

Disadvantages of proprietary channel

Proprietary channels can manage and provide certain automatic functionalities such as setting exchange and management of messaging reliably. But with all these positives they can be the reason of slow adaptation of applications on any new platform. The developer has to wait for adaptation of any new platforms by such channels meaning new proprietary libraries have to be developed for the new platforms, only after these applications can be developed. In most cases using such channels can curb down the usage of open source libraries which might be very convenient otherwise.

Such channels lack abilities to.

1       Adopt new platforms rapidly as they have to build up their SDKs ground up for any new platform in the market.

2       Developers on niche platforms can suffer, since the proprietary channel might not even adapt to a small platform player due to many reasons.

Advantages of HTTP channel

There are innumerable advantages to connecting via HTTP channel and using SUP, a few are listed below.

1       No waiting time for developing for a new platform.

2       Open source libraries can be easily used.

3       Supports native, container based and browser applications.

Capabilities of HTTP channel

1       User On-Boarding. SUP online On-Boarding functionality on this channel is exposed as RESTful OData Web service. Each registration request is a REST based request.

2       Setting Exchange. Applications can request for application related settings through   REST calls to the SUP server.

3       Request Response. Applications can make calls to any http application endpoint (ex Gateway) for fetching business data. For this purpose application shall have to make use of available native http(s) calls.

4       SSL support. SUP server supports SSL over http communication. Any application can open a secure http(s) channel with SUP and utilize it for proxy services.

5       Native Notification support. Any application using this channel can subscribe for notification with the gateway. The notification will be send via native services like APNS, GCM and BIS/BES. For now only three platforms are supported ( iOS, Android and BlackBerry).

1 Comment
You must be Logged on to comment or reply to a post.