[platform-debug-dev] Debug Model Poll - Serialized vs. Concurrent

[Darin Wright <Darin_Wright@xxxxxxxxxx>]

Debug model implementors,

With the introduction of background jobs in the Eclispe 3.0 SDK, the debug 
platform may now access a debug model API from multiple jobs at the same 
time. For example, the debug view may be retrieving labels for stack 
frames while the variables view is retrieving variables for a stack frame. 
This may result in concurrent requests to a debug model API. Note that the 
debug platform was not  built on the assumption that debug models require 
serialized access.

In 3.1, we are extending the use of background jobs to retrieve content 
for the debug view in the background as well. This is to avoid blocking 
the UI while communicating with a remote debug target. This further adds 
to the possibility of concurrent requests on a debug model API. (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=44724)

As the job architecture is part for the Eclispe platform, it is 
foreseeable that other clients may also use jobs to access APIs 
concurrently - i.e. it may not be limited to the debug platform.

My question is, for how many debug models will this present a problem? Is 
your debug model limited to serialized access, and if so, does it 
serialize requests internally?

Thanks,

Darin