quote:
Originally posted by Pai
Starting with the whole discussion about window open/close notifiers, with questions to get the contact's font, and some other things people would like to access but can't with the current script engine, I decided to try and create an ActiveX based Packet sniffer.
quote:
Originally posted by Pai
Examples: (with full commented code)- Window open/close notifier (very reliable, only close notifier has a delay of 15/30seconds from the actual close of the window, due to a WLM limitation )
Your packet analyses is wrong (hence it is not reliable at all actually).
The check of 10th item being '0' or nothing to see if the window was openend by the user or by the client itself isn't correct. Same goes for checking the difference between a closed convo due to timeout or not.
When a user opens a window, the 10th item (datatmp[9]) can also be '0'....
Same for closing a window, when the timeout occurs after x seconds the 3rd item (datatmp[2]) isn't always '0', it can be empty too.
quote:
Originally posted by Pai
My first idea was to make the ActiveX MSN-only (only capture MSN packets), but then I thought that only one extra line of code (check if comming from MSN port) wouldn't matter if you could monitor the entire network.
nice idea...
However, since JScript is relative slow it is maybe advisible to also implement an optional port property in the ActiveX object which you can set before starting the trace
(maybe even making it a string and accept multiple ports as well like "1863;2433;1234").
Setting this property means that the ActiveX internally would check on the port and you don't have to do that anymore in the (slow) JScript.
If the user doesn't set the port property, then trigger for each and every datapacket, as it is now.
PS: playing with this I noticed several bugs, in the displaytoast function and in the stripformatcodes function of Plus! 
/ 
