all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
Adilas API - JSON & WDDX & (XML – later on) - Adilas api calls – cfm - Currently we have both FORM & objects (required change) - Change the order of things - Love it be database driven (later on) vs. custom code or includes… o We might need a mix. Db for standard operations and db plus custom includes for custom work - Doc & DB – built up and detailed out - Setup a searchable sub section of the API - Categorize the documents and pages and methods - Testing or playground environment - 3 step environment: o Prep it o Crunch it (request would look like) o Results (response would look like) - Users, corps, windows, doors, usage, limits, passwords, access, and security issues – not accessible (special) to outside users o Universe level o World level o Who - users, what – permissions & methods, when – ?, where – ip addresses, domains, etc. - Check existing black listed IP addresses - Method password for every call - Who accesses these API calls – history towards the top checks - Run over SSL Brandon & an intern working on the adilas API: - 100+ permissions - $500-1,000 methods - Linker – users; Linker – methods 1. Prep it! – just from fields 2. Convert it! – show it form & cfdump (Full Circle) 3. Run it! – form & cfdump; ½ FORM, ½ objects |