Thanks Dod, As Francois said it likely won't be "easy". It looks like I may have to do some of the same thing you have done.
It looks pretty straightforward to modify FindEventString to copy the data to a match save buffer when a match is detected. Because of the asynchronous nature of the triggers I can forsee a possible problem or two that would have to be worked out... I guess it's time to start digging.... Dave ---- Dod <[EMAIL PROTECTED]> wrote: ============= Hello, Personnaly I do my own buffer storage up to xxx lines and then parse it backward when needed. My buffering is started/stopped upon some triggers. Regards. >> I have a trigger event defined that executes a procedure. >> >> TnScript1.AddEvent(1, '10.10.30.','',[efIgnorecase], >> EventProcessingRoutine); >> >> When the EventProcessingRoutine procedure runs in response to the >> trigger is there a way to see/capture the text string/line that >> triggered the event? I have been going around with this for a couple of >> hours.... FP> It is not easy because data comes from the remote host in packets (usually). FP> Detection is done when the packet has been received but not yet display. FP> Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html FP> -- FP> [EMAIL PROTECTED] FP> Author of ICS (Internet Component Suite, freeware) FP> Author of MidWare (Multi-tier framework, freeware) FP> http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be