Typically what happens is that, when an event occurs in our organisation and action is triggered which creates one file for the event that occured. There are other processes that monitor for these dirs for the xml files and as soon as they appear will handle them. I.e. log/update/close a call in the heldpesk Once these background processes have handled this event xml the file is deleted..

The problem is that if the helpdesk is down, we stop the processes that handle these files. So every time there is an event the files get created but not removed. We would like to keep it like this because then when the helpdesk comes back up we can simply start these processes again and all the event files will be processed (in sequence).

What we need, while the call logging processes are down, is visualisation for the operators. This is what I am trying to accomplish with a view of each dir in a web page. Some way of viewing the contents of the files. I would like to extend this a little also in that if an event is 'Critical' and later there is a corresponding event which changes the status to 'Repaired' I don't want to see this in the web page.

-----
Of all the things I've lost in my life, its my mind I miss the most.

In reply to Re: Re: Fast processing of XML files for CGI by AcidHawk
in thread Fast processing of XML files for CGI by AcidHawk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.