...
| TQL Queries | Restful Services |
|---|---|
XML Oriented (Request & Response) (Note that TQLEngine supports both JSON & XML; the recommended guideline is XML for TQL Queries readability) | Restful Services are JSON oriented |
TQL Queries are sent as payload, therefore the HTTP Method to be used always POST. | Method can be: GET/PUT/POST/DELETE |
When does my role being?
Here is the typical Modeling flow of control:
- Right after initial Model is written, the UI App developer can start working closely to identify (or write) queries.
- Work with Business Analysts to create appropriate UI flows etc
Things you should be aware of?
...
Never hardcode the TQL Query endpoint urls as they are subject to change.
Instead the endpoints must be auto discovered given the project name.
The model developer (owner) will provide you appropriate project name to discover your query endpoints.
- You can test the queries and make sure they are working via Query Editor (TQLStudio or Local TQLEngine)
- Notification frequency and WEBSOCKET reconnect logic.
- Externalize the Queries as much as possible to the App. (Via some config file like: querys.cfg.xml)
- You can serve your UI app (in case of say, HTML/JS) via TQLEngine itself using TQLEngine's ThingSpace / Attach Application feature
Go build some cool app
One of the key difference between Atomiton's TQL platform vs any other middleware platform is that you have the power to write your own queries against the model that is delivered to you by the Model developers.
- Model developers may provide initialization queries.
- You as an UI App developer can decided if you want to combine multiple Find's into one to optimize the rate of transfer.
- Use aliasing to change the output of TQL Query result.