Up to a hundred changes can happen to the data structure every few seconds and there are so many ways to view it, this would mean literally hundreds of thousands of pages that would have to be cached every few seconds just in case some operator decided to have a look at it from just that perspective. (And that's just with the current data set, which is expected to expand tenfold over the next few years)

Presentation logic is built into each object node because only "it" knows how to present itself based on information about the connected nodes and its own capabilities. For instance, if there is a problem somewhere in the network that affects "it" in one of many ways, "it" will show a warning color. This warning state propagates to other nearby nodes like site/area status pages, dynamic maps and so on. Except when an operator has told "it" not to, e.g. because a device is in maintenance mode.

I try not to think of this in terms of web pages but rather as a visual representation/manipulation of a dynamic data structure using SVG glued together with HTML.

It works beautifully. If only I could find a way to do it in paralell, it would be awesome.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.