Hi Justin,
Justin previously determined that this is the case, and in his Log Parsing database that we're using, the plugin command ID's are assumed to start with 3;YYY.
Through a bit of trial and error I can now say with reasonable certainty that in v16 at least, the plugin Commands now appear to start with 1, rather than 3 as was necessary in previous versions of your Debug Log Reader.
A few of the Plugin commands showing up in my Debug Log files take parameters, and so it's relatively straight forward to match them up with the actual commands used in the source. It was just a matter of re-parsing the source Plug-in folder with a different starting ID no each time until the database then indicates that the Plugin calls are from 4D Internet Commands.
Cheers, Allan Udy Golden Micro Solutions Ltd, Blenheim, New Zealand http://www.golden.co.nz<http://www.golden.co.nz> ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
