Overview of WAPL
Remote Solution
In a typical Remote Solution, you make use of Wapple's SOAP API to call functions on our webservers.
- A request comes to your web server for a page on your site.
- Your application performs any neccessary business logic/data manipulation tasks as normal.
- When the data is ready to be displayed to the user, you make a SOAP call the remote Wapple servers, caling the isMobileDevice function, and passing along the device headers.
- If the return value of isMobileDevice is 0, your code carries on as normal, rendering an HTML page to the user.
- If the return value of isMobileDevice is 1, your code generates WAPL instead of HTML.
- This dynamically generated WAPL is then passed to the remote Wapple servers via the getMarkupFromWapl SOAP call.
- The getMarkupFromWapl function returns the perfect markup for the requesting device.
- Your code then sends this perfect markup back to the requesting device.
- The end user sees a perfectly rendered page, and is very happy.
Deployed Solution
In a Deployed Solution, the exact same process is followed, except the SOAP calls are made on your internal network.
The Wapple Exhibit and Architect technologies are deployed onto a server/servers in your own environment, and you make calls to them via SOAP.
You may consider a Deployed Solution if you are intending to generate very high amounts of traffic and/or are concerned about the speed of SOAP calls to remote servers.
If you wish to know more about how we can deploy Wapple technologies in your own environment, please Contact Us