You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The queries of the Process Tree are giving information according to a query time.
This means that the query time is very relevant in the context of the information.
For example, given a specific process information, you might want to query the matching task information (aka thread information). However, to get the info relevant to the given process info, you must query the exact same time. This is very hard to do in a standalone functions without the timestamp integration into the information given. If this info will move between different code components, we can't expect the use to couple them together himself, as it is part of the info.
This problem is even more severe with the lineage query, which gives each ancestor in a different time (according to fork time of its child).
I think that some sort of coupling of the information with the query time is required.
The text was updated successfully, but these errors were encountered:
The queries of the Process Tree are giving information according to a query time.
This means that the query time is very relevant in the context of the information.
For example, given a specific process information, you might want to query the matching task information (aka thread information). However, to get the info relevant to the given process info, you must query the exact same time. This is very hard to do in a standalone functions without the timestamp integration into the information given. If this info will move between different code components, we can't expect the use to couple them together himself, as it is part of the info.
This problem is even more severe with the lineage query, which gives each ancestor in a different time (according to fork time of its child).
I think that some sort of coupling of the information with the query time is required.
The text was updated successfully, but these errors were encountered: