Why need worklight adapter instead direct ajax?

拜拜、爱过 提交于 2019-12-11 21:07:09

问题


I just curious, why we need worklight adapter to communicate with the database? Why not can't using direct ajax? Last time I'm using direct ajax it's not working at all. After I switch to worklight adapter it's running like charm? No problem at all. Why?


回答1:


You did not provide any specific details about your scenario, like Where is that backend system located, if there is any security involved, what is the topology, etc... so why it's not working with AJAX is impossible to answer.

As for why use Worklight adapters, read:

  1. http://javatechig.com/cross-platform/ibm-worklight/how-to-create-a-http-adapter-in-ibm-worlight

  2. Adapters provide templated (adapter types) connectivity settings to various backend systems - HTTP, SOAP, SQL, JMS and so on

  3. Adapters provide a means to auto-generate an adapter for WSDL and sap web services
  4. Adapters can also be pure Java JAX-RS web apps, allow far greater flexibility and functionality (in MFP 7.0)
  5. You must use Worklight adapters if you intend on using the unified push notifications support
  6. Adapters must be used if you intend to utilize any of the Worklight security features (adapter-based, custom login module, device provisioning, custom provisioning and so on)
  7. and so on


来源:https://stackoverflow.com/questions/29381996/why-need-worklight-adapter-instead-direct-ajax

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!