Vladimir Plizga

The issue prevents our project from being fully migrated to Java 8. Is there any plans to fix it? Or there may be a workaround?

From the tests' point of view, the corresponding separation can be achieved by leveraging JUnit's `org.junit.jupiter.api.condition.EnabledOnOs` conditional annotation (see the [doc](https://junit.org/junit5/docs/current/user-guide/#writing-tests-conditional-execution-os)).

@gamefundas You are exactly right. From the very first drafts of AnaLog, browser memory consumption was one of the main concerns to deal with. It is clear that every single...

Ok. Please let me know the results of the testing (when ready of course).

@gamefundas Sure, this is very serious concern. I see two opposite kinds of solution. 1. Just like you've proposed, there can be a single global configuration key that would restrict...

Ok, I will start with implementing the basic restriction which would deny access to any directory outside of specified one.

I've researched the subject and come to the following considerations: - the access restriction settings should be included *not* into choices groups (in `choices.yaml` files) but into global application config...

@gamefundas Yes. Note that the same path can be specified for remote node (I.e. node://pub/home...) but AnaLog agent will restrict it as well.

> Its already released or work in progress This is a released feature. It was initially implemented in v0.7 as a part of composite log support. Then, in v0.11 it...

> this may not work in cases where processes are independent and not discover-able in nature Yes, I totally agree with you and that is why I've mentioned early the...