commandStop() and the in-process execution of snippets

[Grigory Ptashko]

Hello.

I want to implement the in-process execution of JShell snippets without using
the JDI env and a separate VM.

I've studied the ExecutionControl and the RemoteAgent sources and understood how
JShell works in this part. Actually, I've already wrote a simple LocalExcutionControl which allows
executing the snippets in-process. I now see the problem in the stopping of the
client code, i.e. the implementation of the commandStop() method.

So I've got a question. Do I get it right that the JDI was chosen
in order to be able to stop all the client code threads? I mean that a user
is possibly able to create as muany threads as she wants. And the only way to
stop them all at once is executing them in a separate VM?

Do you see any solution to this when launching the client code in-process?

Thank you.

--
Best regards,
Grigory Ptashko

+7 (916) 1489766
grigory.ptashko at gmail.com
facebook.com/GrigoryPtashko