Scenarios Common case Support Java 1.5,1.6 VM (new profiler, views) –Local Europa (via localized remote AC) –Remote AC Europa Uncommon cases (for bkwrd compatibility) Support Java 1.4, 1.5 VM (old profiler, views) –Local Europa (via localized remote AC) –Remote AC Europa Support Java 1.4VM, 1.5 VM (old profiler, views) –Remote AC Pre-Europa F2F decision: Old PI profiler support removed for Java5 in Europa; frees resource but requires probekit port to new agent
Consequences & Options It must be possible to select old profiler & its associated views Option 1: Explicit choice in profiling configuration 1)Java5 Profiling 2)Java 1.4 Profiling (deprecated) 3)Profile with pre-Europa Remote Agent Benefit: Obvious to user what to expect Drawback: Need good names to avoid confusion Option 2: Implicit in VM and AC choice 1.Defer until you choose a VM and AC model. 2.Best match for common case of Java 5 w/ Europa ACs, Benefit: User would not typically see deprecated options Drawback: Complex interaction determines views to be provided. May not be able to configure options serially (to handle backwards compatibility). Drawback: Behavioral differences from pre-Europa is not clearly revealed to user.
Thinking about (Option2) Need to first go to Environment or elsewhere in workbench and select a VM Then views/options available in profiling dialog change automagically How to handle legacy [pre-Europa] AC which uses old PI & views? Just choosing a VM wont give this detail… Suggestion: Option 1