This would satisfy the need to describe anything you’d like about the thread (application, server, vendor, contacts, twists, gotchas, etc…).
I would begin with reference to instructions for cycling the other side of the connection… the application’s Interface Agent
I’d create an html “home page” for each application. From each “home” there would be various additional links to each area of interest for that thread. Multiple threads for a single application could have links on their respective “homes” to a common “application info” page, etc…
I’d need to think about what to document on the hotlinks for PROCS. I guess this would depend on the design of your engine.
