Support multiplexing of spawned debug sessions
Nadie ha tomado este issue todavía.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
From https://github.com/microsoft/debug-adapter-protocol/issues/79, we now have a way for DA's to start client sessions, which spawns new DA's.
However, for many cases, multiplexing the new sessions over the same DA connection is preferable. As a starting point, I suggest the following.
First, to modify StartDebuggingRequestArguments to accept a connectionId?: number.
interface StartDebuggingRequestArguments {
/**
* Requests that the new connection be multiplexed over the same transport
* as the parent session. If present, ProtocolMessages for the new session
* will have a corresponding `connectionId` property. It is not valid to use
* an ID already in use by an existing session.
*/
connectionId?: number;
Then to add a corresponding optional property on the protocol message.
interface ProtocolMessage {
/**
* If the current session was a child started via a `startDebugging` request,
* then this is set to the `connectionId` that was present in the `StartDebuggingRequestArguments`.
*/
connectionId?: number;
And of course add a capability in the InitializeRequestArguments so DA's know whether this is supported
interface InitializeRequestArguments {
/**
* Whether the client supports `connectionId` in `StartDebuggingRequestArguments`
*/
supportsConnectionMultiplexing?: boolean;
- Lenguaje dominante
- HTML
- Estrellas
- 1.8k
- Forks
- 173
- Merge medio
- 7 d 7 h
- PR fusionados (30 d)
- 2
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/debug-adapter-protocol
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
microsoft/debug-adapter-protocol#633 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
microsoft/debug-adapter-protocol#599 · 8 reacciones ·
-
under-discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 48/100
microsoft/debug-adapter-protocol#596 · 9 comentarios ·