Setting the security manager on a method or routine sets the manager for the entire package. This is the way it worked before the concept of a package was exposed in 4.0, so it works a little awkwardly. Had the package concept been there from the beginning, that would have been the only method exposed for doing this.
Rick On Mon, Jul 11, 2011 at 2:34 PM, Jean-Louis Faucher <jfaucher...@gmail.com> wrote: > I implement a (toy) profiler using a security manager to intercept messages > sent to methods. > Currently, I assign the security manager to the method I want to profile > (i.e. monitor the call stack, the call count and the duration) > > A security manager can be assigned to a package, a method, a routine > What is the difference between the three ? Not clear to me how/when the > security manager is called, depending on the object it's assigned to... > > Jean-Louis > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
