...
Gliffy | ||
---|---|---|
|
- We only need to send each class once, thus sent class is always marked as non-sending in the cache.. We will only send if we get the not-known hash basically.
Class sent to CMR
Gliffy | ||
---|---|---|
|
...
- What if an interface is added that would affect the instrumentation of already loaded classes? (your second point above?)
- When nothing is changed we can return null and not send the bytecode again
- I think the saving of bytecode to disc must be added to this chart right away
- Below path (so new class), how would we added methods Ids before we know if we have instrumentations points?
Agent receives InstrumentationResult from CMR (asynchronous mode)
Gliffy | ||
---|---|---|
|
Environment or Profile changed on the UI
Agent in sync mode
Gliffy | ||
---|---|---|
|
- Diagrams might be a slight different for the situation where Profile or Environment is deleted
Agent in async mode